The customer knows first
The tracking page has not updated in four days. Support learns from an angry email, not from an internal alert with context attached.
Custom software for e-commerce operations
Act on delivery exceptions in your business systems, not just the carrier portal
We build shipment monitoring automation for e-commerce teams that need to detect stalled parcels, notify customers before they ask, and trigger operational actions: reship, credit note, next-order hold, not just update a tracking page.
For operators drowning in WISMO tickets, carrier portals, and giacenza while the customer learns about a delay before the team does.
The blind spot
Carrier tools act on the carrier. Nobody acts on your business.
Most shipping software tells you a parcel is late. It does not reship from the right warehouse, create a credit note in ERP, pause the next subscription order, or open the giacenza release task your Italy team handles by hand. The expensive work stays with people because tracking status and business action live in different places.
What a typical fulfillment week looks like
WISMO volume
Where is my order tickets scale with shipments. Agents copy tracking into carrier sites and paste status into the helpdesk, even when the answer is the same delay.
Stalled parcels
No scan for days. Nobody notices until the promised date passes or the customer complains. By then goodwill and reship cost are already higher.
Manual carrier portals
Every carrier has its own login and layout. Ops check reactively because there is no single exception queue tied to orders and customers.
Giacenza and release
In Italy and other markets, parcels can sit in giacenza (carrier or customs hold) until documentation or payment is sorted. Release steps live in email and spreadsheets, not software linked to the order.
No ERP consequence
A delay is visible in tracking but invisible in finance and fulfillment. Credit notes, replacements, and next-shipment holds still require someone to remember the case.
If customers learn about delays before the team does, exception rules are not connected. Tell us your carriers and markets.
The distinction
The problem is not missing tracking links. The problem is that nobody acts on your side when movement stops.
If monitoring only updates a dashboard, the team still has to notice the stall, decide policy, contact the customer, and execute reship or credit in the systems that actually change the outcome. That is where WISMO cost and customer churn sit.
Carrier-centric tracking
- 1Query the carrier for status
- 2Show delay on a map or timeline
- 3A human decides elsewhere what to do
Monitoring with business action
- 1Ingest shipments from WMS, shop, and carriers
- 2Detect exceptions against SLA rules
- 3Notify customer or support with context
- 4Trigger ERP, WMS, or helpdesk actions you define
- 5Log outcome and carrier performance for review
Tracking status and business action can live in one workflow. Let's talk about your shipment process or book a call.
What we build
A monitoring layer that connects tracking events to operational workflows
We do not ask you to replace carriers or helpdesk. We build software that watches shipment status, applies exception rules, notifies the right party, and executes agreed actions in the tools ops and finance already use.
Knowing a parcel is late is information. Reshipping, crediting, or releasing giacenza is operations.
Possible integrations depend on the project. Below are examples of systems we can connect to. It is not a promise that every carrier or platform is already supported out of the box:
Carriers and tracking
- GLS, DHL, UPS, BRT, Poste
- Aggregator APIs where they fit
- Custom carrier feeds
Commerce and fulfillment
- Shopify
- WooCommerce
- WMS / 3PL
- Shipping platforms
Customer and support
- Helpdesk / ticketing
- Email and SMS
- Customer notification templates
- Support automation layer
Back office
- ERP credit notes
- Replacement order creation
- Subscription hold rules
- Internal task queues
It complements support automation: proactive shipment handling reduces tickets before they arrive, while action-based support resolves those that still need a human. Implementations are scoped to carriers, markets, and approval model.
Use cases
Exceptions that can be detected, communicated, and acted on
Exact actions depend on carriers, markets, and what policy allows software to execute versus queue for approval. These are the workflows we design first.
Exception detection
Missing scans, SLA breaches, failed delivery attempts, or return-to-sender patterns flag shipments before the promised date passes without internal awareness.
Proactive customer notification
Late or stalled parcels trigger branded messages with order context, reducing WISMO tickets that only asked for a status you already had.
Carrier performance
On-time rate, exception rate, and giacenza frequency by carrier, lane, and warehouse feed ops reviews with data instead of anecdotes.
Giacenza and release workflow
Customs holds in giacenza create internal tasks, document checklists, and status updates until release is confirmed, instead of living in forwarded email.
ERP actions on delay
Eligible delays trigger credit notes, replacement shipments, or partial refunds in systems finance recognizes, often in copilot until rules are trusted.
Support queue context
When a ticket still arrives, the agent sees shipment status, prior proactive messages, and recommended actions without opening three carrier portals.
These are the workflows we automate first. Which exceptions generate the most tickets or reships today?
Architecture
How a tracking event becomes a business response
Monitoring is software with explicit steps: ingest shipments, normalize carrier events, evaluate SLA and exception rules, notify or execute, log outcomes. Not a passive widget on the thank-you page.
Shipment sources
Shop, WMS, carrier APIs, label platforms
Event normalization
Unified timeline per order and parcel
Exception engine
SLA rules, stalls, giacenza, market-specific cases
Action targets
Customer comms, helpdesk, ERP, WMS
Outcome
Customer notified, action executed, or approval queue
What the implementation typically includes
Multi-carrier ingestion
Polling or webhooks from the carriers and lanes you actually use, consolidated per order instead of one portal per operator.
SLA and stall detection
Rules for no-scan windows, missed delivery attempts, and customs holds in business terms, not just carrier status codes.
Notification and action execution
Templates and API writes for customer messages, tickets, reships, and credit notes, with copilot paths where finance requires approval.
Audit and carrier scorecard
What was detected, sent, and executed, retained for ops reviews and carrier negotiation.
We do not claim every carrier event supports automatic write actions. Discovery separates what to automate, what to notify only, and what stays a human decision by policy.
Economics
Why shipment automation is worth engineering, beyond a tracking page subscription
WISMO tickets have the same economic shape as other repetitive support work: high volume, low variation, expensive people. Proactive exception handling and linked ERP actions reduce ticket load and the cost of late reships, credits, and churn you could have intercepted days earlier.
The ROI logic, without invented numbers
Fewer status-only tickets
Proactive notification on stalls and delays removes a share of WISMO volume that did not need an agent, only an earlier internal scan.
Lower cost per exception
Detecting a stalled parcel on day two instead of day six reduces express reships, goodwill refunds, and repeated contact on the same order.
Ops time out of portals
Hours on reactive carrier sites can shift to reviewing a single exception queue tied to orders and policy.
Carrier accountability
Performance data by lane supports renegotiation and routing changes instead of paying premium freight to compensate for a weak default carrier.
Build vs buy
When custom shipment software is the better economic decision
Sometimes a tracking SaaS product is enough. If standard carriers, branded tracking pages, and email notifications cover the need, subscribe. Custom work is for when exceptions must trigger reship, ERP credit, giacenza workflow, or helpdesk context that generic tracking products do not execute on your side.
Off-the-shelf SaaS
- Branded tracking pages and notifications
- Recurring subscription by shipment volume
- Standard carrier integrations
- Limited ERP or WMS write actions
- Ops still handle business consequences manually
Custom implementation
- Built around your carriers, markets, and SLA policy
- Exception rules tied to orders, customers, and finance
- Giacenza and market-specific workflows where needed
- Integrates with the ERP, WMS, and support you use
- Copilot and autopilot paths you define for credits and reships
- Optional maintenance after handover
Qapla or AfterShip is often the honest answer under roughly two thousand shipments per month with standard carriers and notification-only needs. We will say so if it fits. Custom work makes sense when the carrier dashboard updated but nobody in the company did anything useful.
Engagement
How the work is delivered without rewiring every carrier immediately
Implementation can start with one carrier set and one exception type, such as no-scan stalls, then expand to giacenza workflow and ERP actions. You should see internal alerts before customers on a limited lane before automating credits.
- 01
Discovery
Carriers, markets, shipment volume, current exception handling, and which actions finance allows software to trigger.
- 02
Exception audit
We map how delays are detected today, including giacenza email threads and unofficial portal checks.
- 03
Rules and actions design
SLA thresholds, notification templates, copilot versus autopilot actions scoped to the first release.
- 04
Build and integration
We connect shipment sources, carriers, and target systems with approved credentials.
- 05
Shadow monitoring
Exceptions fire internally alongside the current process. Teams compare alerts to reality before customer-facing automation.
- 06
Rollout and expansion
Add carriers, markets, and write actions progressively. Optional maintenance when carriers and policy change.
We do not quote a universal timeline or fixed package price on this page. Duration follows carrier count, action depth, and how many market-specific cases belong in the first release.
Start with one carrier set and one exception type. Expand when alerts match reality. Book a call.
Questions
Direct answers
Let's map what should happen when a parcel stops moving
Bring your carrier list, monthly shipment volume, and a recent delay handled badly. We will tell you what is realistically automatable, what stays in copilot, and when a tracking SaaS is the more honest recommendation.