...
We can use various integrations methods to connect to the client’s ERP system so that data can be transmitted from (or to) Seko SEKO systems. The common integrations methods used are API, EDI, or via flat files (like XML or CSV). Flat files like excel and CSV are not preferred options since most of the time these files are created manually and are prone to human typo errors.
...
We can connect to partner APIs to send/receive data (e.g. Shipment Booking). This will require development effort at our end.
What do we need from the partner for API:
API endpoints → Providing information on how to connect to their system
API documentation → Providing details on each field/parameter for the API
A technical contact (from the partner-side) for testing and answering any questions related to the development
...
Partners can connect to SEKO API’s to send/receive data. We do not have any development effort on this other than providing credentials to client. The documentation for Seko SEKO API’s can be found here.
SEKO API’s can be used to connect to:
Domestic system for quoting, booking and status
CargoWise One for booking and status.
| Info |
|---|
EDI |
EDI (Electronic Data Interchange) is electronic exchange of business documents such as orders, invoices, shipment status etc. These documents are transmitted between the business partners in the form of structured data (aka specification document).
What do we need from the client for EDI:
EDI Specification document.
EDI Connection Type (AS2, VAN or sFTP)
A technical contact for testing, or answering questions related to the setup/document
...
EDI# | FUNCTION | DESCRIPTION | CATEGORY | SPECIFICATION |
|---|---|---|---|---|
EDI 110 | AIR shipment Invoice | Invoice for Air shipments | Shipments (Mode: Air) | |
EDI204 | Load Tender | Used by shipper to offer or tender truckload or LTL shipment to a carrier | Shipments (Mode: Ground Transport) | |
EDI 210 | Invoice | Pricing for services | Invoice (Mode: Ground Transport) | |
EDI 211 | BOL for Motor Carrier | Motor Carrier Bill of Lading | Shipment (BOL) | |
EDI 214 | Status Message | Gives the buyer a status of their shipment | Shipment Status (Mode: Ground Transport) | |
EDI 310 | Ocean Shipment Invoice | Invoice for ocean shipments | Invoice (Mode: Ocean) | |
EDI 315 | Ocean Status | Status update for ocean shipment | Shipment Status (Mode: Ocean) | |
EDI 850 | Purchase Order | Customer orders product to ship to SEKO warehouse | Warehouse | |
EDI 855 | Purchase Order Acknowledgement | Response to EDI 850 | Warehouse | |
EDI 856 | Ship Notice / Manifest | Supplier sends to customer for notification about upcoming delivery of shipment | Warehouse | |
EDI 860 | Goods Receipt | Return message confirming products received in purchase order | Warehouse | |
EDI 861 | Inventory Summary | Summary of stock on hand at SEKO warehouse | Warehouse | |
EDI 888 | Parts Master | List of products that SEKO will stock on customers' behalf | Warehouse | |
EDI 940 | Sales Order | Request for shipment from SEKO warehouse to buyers' location | Warehouse | |
EDI 944 | Warehouse Stock Transfer Receipt Advice | To confirm the receipt of a shipment | Warehouse | |
EDI 945 | Ship Confirmation | Return message confirming shipment has been shipped | Warehouse | |
EDI 990 | Response to Load Tender | Response to EDI204, determines whether carrier will pick up shipment | Response for EDI 204 | |
EDI 997 | Functional Acknowledgement | Response to the received EDI transactions | Response for any EDI transaction/document |
...