A test order reaches the inventory system and receives a tracking reference, so the team declares the integration ready. After launch, a cancelled order remains committed and a damaged return becomes available to sell. Connectivity may work while the quantity rules the store needs remain untested.
Shopify integration acceptance needs separate cases checking stock meaning at a particular location for an identified product variant. Before the session, agree each quantity's source and changing event, then record starting state and expected outcome. A successful order should not replace this map.
Which quantity will the integration display?
Shopify documentation distinguishes on-hand, available, committed, unavailable and incoming inventory not yet received. Do not map an ERP field called “stock” to a displayed Shopify number without defining it. One may be a total while the other is sellable quantity after exclusions.
Ask the developer to identify the field, its update owner and representation of states without direct equivalents. Do not automatically include warehouses that do not serve the store in online availability. Location selection and selling-after-stockout policy are agreed configuration decisions that should appear in the test evidence.
A small sample with clear references
Imagine a fictional luggage store with two variants and two locations. For the gray variant in the first location, assume ten units on hand: three committed, one unavailable and six available. These are teaching figures under the sample's stated definitions, not real store data or a rule for every ERP.
Keep variant and location identifiers and their mappings to the other system. Names and colors are insufficient when descriptions change or repeat. Add cases for the other variant and second location to reveal mapping errors instead of succeeding by coincidence because the sample contains only one item.
Six tests that should not become one order
| Test | Observe | Acceptance evidence |
|---|---|---|
| New order | Quantity changes in the agreed state and location. | Order reference linked to before-and-after stock snapshots. |
| Cancellation before fulfillment | The restock option and approved policy. | Released quantity or documented retention without duplicate addition. |
| Fulfillment or dispatch completion | State transition without an unintended second deduction. | Explain on-hand, available and committed quantities afterward. |
| Resellable and damaged returns | Different availability decisions after inspection. | A known effect for each item, separate from refunding money. |
| Stockout at one location | Permitted sales and fulfillment source. | Policy-compliant behavior without borrowing excluded location stock. |
| Source quantity correction | Update arrival, direction and conflicting writes. | Variant/location reconciliation with explained update timing. |
This is a proposed acceptance matrix, not automatic behavior of every connector. The provider tests actual settings and interface capabilities. If return handling is excluded, the proposal should explain its manual stock effect and review owner instead of claiming complete synchronization.
Cancellation does not define the restock policy
Shopify documents a restocking option on cancellation and a timeline recording restocked and refunded items. Review that choice and its connector effect rather than assuming every cancellation adds quantities identically. This is technical scoping guidance, not a discussion of refund obligations or consumer law.
In the luggage example, one returned item may be sellable while another needs inspection. A financial refund event should not alone authorize making both available. Identify who approves condition and which system issues the change, then test its arrival at the intended destination.
Reconcile after events have settled
Add event time, result visibility time and the reference linking both records to the test log. Synchronization may run periodically; the project defines acceptable timing and delay detection. Do not mix snapshots taken before and after updates and call the difference a defect or agreement without explanation.
Request discrepancies a stock owner can understand: variant, location, quantity state, expected and actual values, and a reason or follow-up action. Connectivity interruption and event resubmission are covered in integration failure and retry tests. Here the focus is stock meaning after processing.
The integration input map helps before pricing. When purchasing Shopify services from Nextwave, include sample cases and reconciliation records in handover. You can then accept an operational result rather than merely prove that two systems exchanged a message.
References and preparation
Shopify's inventory state guide and order cancellation guide were opened on 3 November 2026. They support the distinctions and restocking option. The example and tests are editorial proposals. AI assisted preparation with information and source review.
