Chapter 9: Testing, go-live and support

End-to-end test

1. Sync your locations and confirm they appear in Pipe17 linked to your integration.
2. Turn on products.out and confirm your test SKUs reach your system.
3. Place a test order on a connected selling channel (or create one with POST /orders) and confirm a Shipping Request is routed to your location.
4. Confirm your connector picks it up, creates it in your system, and the request moves to sentToFulfillment with your ID in extReferenceId.
5. Ship it in your system and confirm the Fulfillment appears in Pipe17 with tracking, and the request moves to fulfilled.
6. Push inventory and confirm the levels on the SKU's inventory page.

Failure tests

• Stop the connector for an hour, restart it, and confirm it catches up with no gaps or duplicates.
• Send the same webhook twice and confirm it is processed once.
• Order a SKU your system does not know and confirm an Exception appears on the Shipping Request.
• Cancel an order before it ships and confirm your system stops it.
• Ship an order in two packages and confirm two Fulfillments and a final fulfilled status.

Go-live checklist

• Production keys stored in a secrets manager
• State store backed up
• One copy of each poll job at a time (locks in place)
• Webhook endpoint on HTTPS and checking the shared secret
• Polling still on as the safety net
• Retry queue, Exceptions and alerts working
• Flows turned on in Settings one at a time, starting with Locations and Products
• First live orders watched through to fulfillment

Need Help?

• Pipe17 API reference for every endpoint, field and status. A machine-readable OpenAPI spec is linked from the same site. A Postman collection with every call in this guide is attached to this article: import it and set the baseUrl, integrationKey and connectorKey variables.
• Use Ask Pippen, our AI agent, located at the top of the app page.
• Submit a support request with as much relevant detail as possible. Learn how to submit a request.