What does this integration do?
The Aras Kargo integration opens a shipment record in the Aras system automatically for orders placed on Shopify, generates the shipping barcode, and writes the resulting tracking number onto the order so the customer can be notified.
The data it synchronises
Order → shipment record
Shipping barcode / label generation
Tracking number written to the order
Shipment status updates
Bulk shipment creation
Return / cancellation scenarios
How the data flows
01
The order becomes ready
We decide together which event triggers the shipment record: payment confirmation, or the warehouse marking it picked. Prepaid and cash-on-delivery orders are set up differently.
02
The shipment record is opened
Recipient details, address and volumetric weight are written into the Aras system. If product weights are defined in Shopify the calculation is automatic; if not, every order needs a manual correction.
03
The barcode is generated
Labels are printed from the admin or in bulk. If your daily shipment count is high, we build the bulk printing screen around your warehouse flow.
04
The tracking number is written to the order
The number is written onto the Shopify order, the shipping notification email is triggered, and the customer can track it from the order page.
05
Statuses are read back
Out for delivery, delivered and undeliverable statuses are reflected on the order. We set up a separate follow-up list for undeliverable shipments.
What we watch for in this integration
Volumetric weight and weight fields must come from product data; blank fields lead to wrong shipping charges and invoice discrepancies
Province and district matching in address fields must follow the format the carrier expects; free-text addresses cause the shipment record to fail
If cash on delivery is used, the collected amount must match the order exactly, and how reconciliation works is defined up front
Branch pickup preferences go in a dedicated field, not the order note; information in a note cannot feed automation
On return shipments, who generates the return code — the customer or the store — is a process decision
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
Aras Kargo customer number and API user credentials
Your negotiated price list, with any region/volumetric breakdown
The state of weight and dimension data on your products
Average daily shipment count and number of warehouses
Whether cash on delivery is used