EDI & API INTEGRATION
Connect each depot to each shipping line without losing message-level control.
Integrate container depots with shipping lines using depot-specific codes, configurable mappings, EDI/API messages, retries, acknowledgements and reconciliation.
THE OPERATIONAL PROBLEM
What ECY 360 is designed to eliminate.
- !One depot has different codes across shipping lines and manual mappings cause rejection.
- !A technical delivery success is mistaken for business acceptance.
- !Retries create duplicate inventory or billing events.
- !Support teams cannot see the original payload, transformation, response and operational result together.
CAPABILITIES
Controls that work at the point of operation.
Partner and depot mapping
Maintain the customer's depot code, line code, location code and reference translation per connection.
Message profiles
Configure supported EDI/API message types, versions, directions, schedules and mandatory fields.
Transformation rules
Map external values to governed ECY 360 owners, ISO types, statuses, customers and operations.
Idempotent processing
Detect duplicate external messages and prevent repeated business effects.
Acknowledgement tracking
Separate sent, delivered, technically accepted, business accepted and rejected states.
Replay and reconciliation
Correct mappings, replay eligible failures and compare partner totals without losing history.
END-TO-END WORKFLOW
Where the process starts, advances and closes.
- 01
Receive or emit
Accept API, file or message traffic through the configured partner channel.
- 02
Validate envelope
Check partner, depot code, message type, version and duplicate identity.
- 03
Transform and validate
Convert partner fields to governed master data and business commands.
- 04
Apply business event
Create the instruction, movement, status or response inside the correct tenant and depot.
- 05
Acknowledge and observe
Return the configured response and track the complete processing timeline.
BUSINESS OUTCOMES
Operational control that pays for itself.
Correct partner context
Every line and depot uses the codes and validation profile expected by that connection.
Retry without duplication
Idempotency and message identity prevent repeated operational side effects.
Supportable integrations
Operations and technical teams can trace payload, mapping, acknowledgement and business result.
FREQUENTLY ASKED QUESTIONS
Clear answers before your demo.
Can the same depot have a different code for every shipping line?+
Yes. ECY 360 stores customer-facing depot codes and reference mappings per integration partner and depot.
Which EDI messages are supported?+
The integration framework is message-profile based and can support agreed equipment movement, status, instruction, estimate and acknowledgement flows such as CODECO where required by the line.
What happens when a message fails?+
It is recorded with its stage and reason, alerted according to policy and routed to retry, mapping correction, replay or manual reconciliation without deleting history.
YOUR DEPOT. YOUR RULES. ONE PLATFORM.