Record field mapping as the working agreement
Document the source system, destination field, required status, format and quantity unit for each field. Define clear rules for SKU, location and order reference. Deliberately test unknown items and missing required fields to verify the agreed error handling.
Test repeated and out-of-order updates
Resend the same test order and check that a second dispatch order is not created. A delayed update should not silently replace a later state already confirmed. Document expected and actual results and related references for each test case.
Plan failure and recovery together
When a connection is interrupted, record which orders remain open and which system continues processing. Reconcile the last confirmed state before resending updates. Record launch approval, contacts and the exception procedure in writing.
Plan step by step
- Define a unique SKU for each item and a unique reference for each order. Agree field names and required data with both teams.
- Prepare test data without real customer details. Check a complete order, a duplicate reference and an invalid address.
- Review changes, cancellations and partial shipments. Define who decides on exceptions and how errors are reported.
- Reconcile inventory and shipping information and document launch approval. Exchange credentials through the agreed secure method.
The CSV records test cases and approvals. Use test data and keep credentials in the agreed secure channel.
Next step
Bring your product profile and the open questions from this guide to the conversation. Our team will agree services and handling with you.