The integration is not one system, it is two
A TSS API project is really an ERP-to-TSS integration. The TSS side is well documented. The ERP side is where every project spends its time.
Establish the source of truth
Product data, party data and consignment data each need one authoritative home. If the ERP does not currently own them, the integration will drift within weeks. The TSS integration analysis puts this first for a reason.
Map fields to specifications
Every TSS field needs an ERP field or a computed value. Where a computed value is used, document the logic and version-control it.
Design for two-way traffic
Submissions go out. Responses come back. Both need to update the ERP so the audit trail is complete on one side.
Handle exceptions without breaking the ERP flow
Rejected submissions should not corrupt ERP records. A separate exceptions area, tied back by reference, keeps the ERP clean.
Keep the portal available
Hybrid coverage matters even after a full integration. Controlled goods, new suppliers and unusual movements often still route through the portal.
See a TSS-to-ERP integration with hybrid portal fallback. Watch a demo.
Top comments (0)