ForgeWP

Commerce Deployment and Known Limits

Verify product, cart, account, shipping and checkout behavior before accepting a real WooCommerce deployment.

Commerce deployment and known limits

This is a source-reviewed documentation foundation. The module remains outside the indexed/AI-reader publication set while its integration contract is reconciled. Package-wide typing currently fails on cart/provider inconsistencies and transitive React-preview dependency errors. Checking individual examples does not close those failures.

Acceptance checklist

  • Verify real product IDs, visibility, variations, stock, currency and product URLs with WooCommerce active.
  • Check catalog pagination, exported loops, empty results, HTTP failures and subdirectory installations.
  • Reconcile provider/standalone state and return contracts before combining components.
  • Verify guest/signed-in cookies, nonces, reload persistence, cart merging and empty-server-cart behavior.
  • Test add/update/remove/clear, coupons and shipping against registered routes; resolve known method and missing-route mismatches.
  • Reconcile commerce account hooks with current Auth JSON/nonce requirements. Reject false successful logout and test expired sessions.
  • Check private order/download ownership, profile/address permissions, review moderation and wishlist failures.
  • Implement and verify the selected payment flow, gateway inputs, success/failure/cancellation, duplicate submissions and correct order-status transitions. The current custom order handler does not process payments.
  • Validate server prices, stock, taxes, shipping and discounts. Preview arithmetic does not establish store rules.

Common symptoms

Table · 2 columns
Symptom
Inspect
Products appear after an endpoint error
Catalog fallback to mock/hydrated products
ID/SKU lookup misses a product
Collection-only lookup and pagination
Missing drawer/cart-row fields
Provider versus standalone state mismatch
Badge changes but server does not
Optimistic state, ignored failed responses, session or route mismatch
WordPress stays signed in after logout
Commerce hook omits current Auth JSON/nonce contract
A payment method remains visible after request failure
Hook defaults are not enabled-gateway acceptance
An order succeeds without a charge
Custom handler creates orders without gateway processing

Reproduce failures on an isolated store. Do not clear real customer data or weaken nonces/permissions to make a local interface appear successful.