Reconcile a hosted quantity change with the store’s reservation

Establish which quantity crossed the system boundary

Start with the same product or variation across the initial cart, store reservation, final Checkout line items and paid order. A matching display name is insufficient when different variations share a title. Record timestamps and internal references so an earlier Session or later order edit is not mistaken for the final purchase.

Stripe’s hosted Checkout guide describes line items supplied through Price references or explicit price data and lists adjustable quantities as a feature. A permitted change on the payment page can therefore alter the quantity the buyer pays for after the store first recorded its cart. The guide does not establish what any particular WooCommerce connector does with that change. Record whether adjustment was actually enabled on the affected flow; feature availability alone is not evidence that it caused this mismatch.

Confirm that stock was really reserved

Read the reservation record and the inventory settings, not just the cart quantity. WooCommerce’s inventory documentation distinguishes quantity management from a stock-status label: with stock management off, a status does not supply a count. Its Hold stock setting applies to Pending payment orders, not On hold orders. Do not treat similarly named states as interchangeable or infer a held quantity from the public availability wording.

Keep the original reservation quantity and its time even if the hold has since expired or been released. Beside it, record any later release, replacement reservation or stock deduction that the store’s own history shows. If the connector or another inventory system owns those movements, identify that system. Core WooCommerce settings cannot establish its synchronization behavior or reconstruct a missing reservation history.

Calculate the difference without applying it twice

For each matched item, subtract the original reserved quantity from the final paid quantity. A positive result means the paid purchase required more units than the earlier reservation covered. A negative result means the earlier reservation covered more units than the paid purchase required. Zero means no quantity difference for that item; it does not prove the reservation is still active or that the stock deduction occurred correctly.

Next compare the final paid quantity with the store order quantity. If they disagree, preserve both readings and identify the point where the hosted quantity failed to reach the store. If they agree, inspect inventory movements before deciding stock is reconciled. The integration may already have released the original hold or deducted the final quantity. Applying the calculated difference without reading those movements can repeat a correction.

Give the inventory owner the original reservation, final paid requirement, recorded movements and remaining unexplained difference. Ask the owner to identify the required net action against current stock. If the additional units are unavailable, leave fulfillment unresolved under the merchant’s actual order process; payment is not evidence that the units exist. Do not invent a stock count, silently substitute items or ask for another payment to settle a quantity record.

Define the handoff and the evidence that closes it

The reconciliation owner needs a narrow finding: which matched line changed, whether the store order adopted that quantity, and whether stock movements account for it. Separate correction of this order from the decision about allowing future quantity edits. Keeping adjustable quantities, constraining them or removing the control requires confirmation of what the actual integration supports and how its reservation handling will work.

A useful closure record connects the final paid items, corrected store quantities and documented inventory action, with any fulfillment exception still named. For a Prism checkout consultation, summarize that mismatch, the platform and the affected public journey. Confirm implementation responsibilities, scope, fees and terms before work. Use the public inquiry for the question, without customer exports or private payment links; it does not purchase a repair or submit a processing application.

Quantity-reservation comparison

Use a separate copy for each real product or variation in the affected order. Compute the quantity difference only when both inputs are known. It describes changed demand; later stock movements determine what, if anything, still needs correction.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.