SignalEDI | Partner onboarding preparation checklist Planning worksheet, not a certification or permission to send production data. Use your partner's current implementation guide and confirm scope during setup. Partner and program: _________________________________________________ Supplier/vendor ID (record privately): ________________________________ Business system and edition: _________________________________________ Requirements owner: ___________________ Target review date: ___________ 1. Define the program [ ] Identify the retailer, brand, division and fulfillment model. [ ] Distinguish warehouse/DC, direct store delivery, dropship and non-resale. [ ] Obtain the current partner-issued guide, revision and test packet. [ ] Confirm which requirements are mandatory, conditional or not applicable. 2. Identify data and access owners [ ] Agree which system owns orders, items, prices, shipments and invoices. [ ] Confirm connector edition, operations and account permissions. [ ] Assign owners for identifiers, units of measure, lots, dates and labels. [ ] Use synthetic or appropriately scrubbed samples during preparation. [ ] Keep credentials, customer data and sensitive identifiers out of this file. 3. Map the required exchange [ ] List document codes, versions, direction and required business fields. [ ] Confirm transport, endpoints, envelope IDs and receipt expectations. [ ] Record acknowledgements separately from business acceptance responses. [ ] Reconcile PO, shipment, invoice and physical-label references. 4. Test the outcomes [ ] Valid order and response follow the assigned workflow. [ ] Missing fields and invalid identifiers produce actionable errors. [ ] Duplicate submission or retry does not create a second business outcome. [ ] Partial shipments, quantity changes and cancellations are handled correctly. [ ] Invoice grouping, units, prices and destination match the partner rules. [ ] Rejected documents can be corrected with an auditable history. [ ] A timeout is investigated before retrying an uncertain delivery. 5. Agree the production boundary [ ] Obtain the partner's written approval for the tested program and version. [ ] Confirm production credentials, endpoints and runtime availability separately. [ ] Establish monitoring, exception ownership, rollback and reconciliation. [ ] Keep approval evidence, test results and known exclusions with the change. [ ] Do not confuse sample validation, a portal login or a listing with go-live. Open questions / evidence needed: _____________________________________________________________________ _____________________________________________________________________ Start: https://signaledi.com/guides/customer-requires-edi Integration scope: https://signaledi.com/integrations Current pricing: https://signaledi.com/pricing Current platform status: https://signaledi.com/status