Testing your Shopify fulfilment setup

Set the test scope

Use the test-order instructions for your connection. Check whether the test uses a simulation or a real charge and production order before submitting it.

Choose a representative product and variant. Include additional variants where they exercise a different size, artwork or delivery rule.

Run the checklist

1. Confirm store access and product mapping.
2. Check the product information, garment and artwork.
3. Create the test order using the specified route.
4. Verify the order and recipient details received by fulfilment.
5. Check payment and release conditions.
6. Confirm the expected status and tracking update.
7. Record the test outcome and any issue.

A green connection status alone does not complete this checklist.

Check an exception

Use the agreed safe test scenario for an unmapped or incomplete order. Confirm that it is held with a useful message and can be corrected without duplicate production or charging.

Keep synthetic customer details in test screenshots and records.

Complete readiness

Resolve failed checks and repeat the affected test. Confirm the go-live action only after the required checks pass.

If a test result is uncertain, inspect the original order and payment record before trying again. Include the connection, test reference and visible error when asking the team for help.

Define a pass before the test

Agree whether the test is simulated or will create a charge and a physical item. Choose an authorised delivery recipient. Record the expected garment, colour, size, artwork version, position, price and delivery method before submitting anything.

Keep evidence for each stage

• One store order is linked to one fulfilment reference.
• The received specification matches the chosen variant and artwork.
• The payment and production-release result matches the agreed test.
• The parcel presentation and any garment labels match the service arrangement.
• The dispatch message reaches the intended recipient and its tracking link belongs to the right parcel.
• An agreed exception can be resolved without a duplicate order, charge or production job.

Sign off the result

Mark each check as passed, failed or not tested. Record a screenshot or reference for a pass, and a named next action for a failure. Keep a launch paused when a required result is uncertain. A successful login or a green connection message alone is not an end-to-end test.