Known SalePro Limitations for the Current Release Candidate

These boundaries are customer-facing product facts for the inspected release candidate.

Payments and external providers#

• Legacy PayPal POS tender is rejected before canonical receipt creation. Do not treat a browser success response as settlement.
• Mpesa is not a durable, authenticated, currency-bound canonical POS settlement bridge. Keep live initiation/tender disabled unless a separately certified integration is delivered.
• Automated tests use fake providers; they do not prove live capture, refund, webhook, credentials, callback URLs, or provider dashboards. Reconcile live provider accounts operationally.
• A failed or pending Stripe compensation is recorded for manual provider reconciliation; never blindly retry a charge or refund.

Inventory and transaction identity#

• Historical purchase-return rows may have unknown source-line provenance. SalePro does not invent it. Review ambiguous records individually.
• Imported Damage, Production, and Repair support only identities their workflows can retain. Unsupported batch/IMEI/serial combinations are rejected.
• An exchange involving imported source or replacement stock is rejected to protect FIFO history. Record a sale return and then a new sale.
• IMEI/serial storage has legacy text-based constraints; do not promise per-identifier specific costing.
• Batch/expiry data does not imply automatic FEFO picking or a universal hard expiry-sale block.

Restaurant#

• Public-menu ordering accepts at most one canonical variant for a cart line; arbitrary multi-option variant combinations are unsupported.
• Reservation collision checks do not model duration ranges. Staff must prevent overlapping reservations with different start times.

Tax and currency#

• India GST reports are operational registers/reconciliation aids, not direct GSTN filing.
• Foreign-currency India GST statutory presentation has no approved conversion policy. Use the reviewed INR scope only until a tax/finance owner approves and validates another policy.
• Invalid or missing historical FX snapshots fail closed and require reconciliation; SalePro does not infer historical rates.

Modules and distribution#

• Tailoring, Gym, and the full ZATCA KSA module package are absent from this repository even though registry/status/sidebar references exist. A status flag alone does not make them available.
• Ecommerce and WooCommerce are bundled but administrator-enabled. Enabling them does not provide third-party services, credentials, WordPress, WooCommerce, hosting, or payment accounts.
• WooCommerce has no active webhook receiver or background sync schedule in the inspected package. Sync is manual, and live endpoint behavior is not certified.
• WooCommerce order import is unavailable in ZATCA Phase 2.
• Module manifests do not declare versions or a compatibility range. Distribution assets still require human legal review and third-party notices.

Operations#

• Protected updater/version-upgrade behavior was outside the certification and documentation-change scope.
• Existing production/customer data was not changed or repaired during this documentation pass.
• Screenshot accuracy remains a publication task. Every legacy screenshot is provisional until checked against the certified UI.