Automated Shipping Logistics: Tracking Without Humans

In any ecommerce or SMB that ships orders, there's one question that repeats to the point of exhaustion: "where is my order?". Automating shipping logistics means integrating the APIs of carriers and couriers (Andreani, OCA, Correo Argentino, Chilexpress, Servientrega) into a centralized tracker that checks every shipment, detects the events, and notifies the customer via WhatsApp or email automatically — with no human in the middle. The number that justifies the project: "where is my order" (WISMO, as the industry calls it) is usually 50-70% of all support tickets in an online sales operation.

The invisible cost of answering "where is my order?" by hand

Let's put conservative numbers on it. An operation shipping 800 orders per month typically gets 250-400 tracking inquiries. Each one means: reading the message, looking up the tracking number, going to the carrier's website, interpreting the status, and writing the reply. That's 4-6 minutes per inquiry: between 20 and 40 hours a month of one person acting as a middleman between two systems that could talk to each other on their own.

And the worst part isn't the hours: it's that the customer asks because they're anxious or distrustful. Every tracking inquiry is a micro-crack in trust that, automated, wouldn't even happen.

How carrier APIs work in LATAM

Each courier exposes (with varying quality) services for two moments:

• Label generation: create the shipment from your system, get the tracking number and the label. This alone eliminates the manual work on the carrier's website.
• Tracking: query the shipment's events (accepted, at facility, out for delivery, delivered, returned).

The regional landscape, summarized:

Carrier	Country	Integration	What makes it stand out
Andreani	Argentina	Documented REST API	The most mature on the Argentine market
OCA	Argentina	Web services (e-Pak)	Works, but it's SOAP from another era
Correo Argentino	Argentina	Integration via ecommerce platform	Unbeatable nationwide coverage
Chilexpress	Chile	REST API with developer portal	Solid technical standard
Servientrega	Colombia	API / web services	Requires a commercial agreement

Two realities to keep in mind: first, each API speaks its own language — the event Andreani names one way, OCA names differently, and another carrier doesn't report at all. Second, not all of them notify in real time: some require periodic polling. That's why the right architecture combines scheduled queries with notifications where they exist — the exact trade-off we analyze in cron jobs vs webhooks.

Architecture of a centralized multi-carrier tracker

What we build in these projects has four layers:

1. Per-carrier connectors: one module per courier that knows how to authenticate, query, and translate. If tomorrow you switch carriers or add one, you add a connector without touching the rest — classic API and integration development work.
2. State normalization: every event maps to your own simple set: prepared, dispatched, in transit, out for delivery, delivered, delayed, returned. The customer never sees the carrier's internal jargon.
3. Event and alert engine: every status change can trigger actions. The typical ones: WhatsApp on dispatch ("your order shipped, arriving Thursday"), an out-for-delivery alert ("arriving today, make sure someone's home"), a delivery confirmation with a one-question survey.
4. Proactive delay detection: the crown jewel of the system. Rules like "no new events for 72 hours" or "passed the promised date" flag the shipment as delayed and trigger: an alert to the customer before they ask, an automatic claim to the carrier, an internal alert if the order amount is high.

On alert channels: email is free but rarely read; WhatsApp has open rates of 90%+ and a per-conversation cost of USD 0.03-0.08 via the WhatsApp Business API — for 800 orders/month with 3 alerts each, we're talking about USD 70-190 a month that pay for themselves with the tickets they prevent.

Does your support team spend the day answering "where is my order?" Book a 30-minute call and we'll calculate how many tickets an automated tracker takes off your plate.

The metrics that justify the project

Results we've seen in real implementations (conservative ranges):

• WISMO tickets: −50% to −70% in the first 60 days. An apparel store shipping ~1,200 orders/month went from ~420 monthly tracking inquiries to fewer than 140.
• Administrative dispatch time: −80% when label generation is also automated (the label and tracking number generated straight from the sales order).
• Formal complaints over delays: −30% to −40%, because the proactive alert defuses the anger before it escalates.
• Unexpected bonus: your own data on each carrier's real performance by zone. More than one client renegotiated rates — or switched carriers in certain regions — with that evidence in hand.

What it costs and how long it takes to build

Conservative ranges for 2026, based on what we've seen in real projects:

• Integration with a single carrier + email alerts: USD 1,500-3,000, in 2-3 weeks. The typical entry point.
• Multi-carrier tracker (2-4 carriers) + WhatsApp alerts + delay detection: USD 4,000-10,000, in 4-8 weeks. This is where most of the value sits.
• Monthly infrastructure: the server and messaging rarely exceed USD 100-250/month all in.

Against 20-40 monthly support hours recovered plus the complaints that never escalate, the typical payback is between 5 and 10 months. And it's best to roll it out in stages: start with the carrier that handles the most shipments, measure the drop in tickets over a month, and only with that number in hand add the rest of the carriers and the more sophisticated alerts.

For logistics operators: the same system, a different scale

If instead of selling online you are the logistics operator, the centralized tracker becomes a product: a portal where your clients (the ecommerce stores that hire you) see their shipments, configure their alerts, and download reports. That's already a custom management system with tracking at its core, and it's usually the commercial differentiator against operators who send an Excel file by email. For your own fleet, the visibility layer can extend to a mobile app for drivers that feeds the events in real time.

When NOT to automate tracking

• Fewer than 100 shipments per month: the inquiries take minutes a day to answer; spend that budget on something else (probably on selling more).
• A single carrier with good native notifications: if you ship everything through one courier whose platform already sends decent emails, the marginal improvement is small. Multi-carrier is what changes the game.
• Your problem is the physical operation, not the information: if shipments are late because the warehouse dispatches late, automating alerts will only help you communicate the bad news faster. Fix the process first, then the software.
• You expect the carrier to improve: automated tracking gives you visibility and communication, but it won't make OCA reach Río Gallegos any sooner. Manage expectations (yours).

From tickets to a system that pays for itself

If your multichannel operation already syncs stock and prices — as we covered in ecommerce automation with MercadoLibre — automated tracking is the natural next step: the same order that draws down stock generates the label, fires the alerts, and closes the loop with confirmed delivery.

At Deepyze we integrate carriers from Argentina, Chile, and Colombia into centralized tracking systems with WhatsApp alerts and delay detection, for ecommerce stores and logistics operators. A fixed price agreed before we start, a concrete proposal in 24 hours, and a team in your own time zone — one that's awake when your Hot Sale explodes. Tell us how many shipments you handle and with which carriers and we'll come back with an architecture and a concrete number.