Staff visit multiple carrier sites and compare services for every order.
All focused services
05Shipping rate automation
Choose, buy, and print the right label automatically.
We use the order, package, destination, inventory, carrier, cutoff, and delivery promise to select the lowest-cost eligible service—then purchase and print the label without manual comparison.
AWhere it shows up
Usually, the warning signs look like this.
The cheapest rate is selected without checking the promised delivery date—or vice versa.
Tracking, shipping cost, and label changes are keyed back into other systems manually.
Nobody knows a shipment is late until the customer calls to ask where it is.
Refunds for missed service commitments go unclaimed because nobody compares deliveries against the commitment inside the carrier’s filing window.
Delay information lives in a carrier portal that the people answering customers cannot see.
BThe operating path
Built around the real handoffs.
This is the common shape—not a prepackaged connector. During feasibility, we confirm the actual access, rules, volumes, exceptions, and definition of done.
Read the order
Collect destination, package, service commitments, special handling, and fulfillment location options.
Rate-shop
Request eligible carrier services and compare landed cost against delivery time and operating rules.
Purchase + print
Buy the selected label, store the documents, and route it to the correct printer or packing station.
Watch the promise
Write tracking and cost back to the order and CRM, measure each delivery against the service commitment that was purchased, and escalate a miss before the customer notices it.
B1Featured build
When: A shipment misses the delivery date it was sold onOne hub that turns a late delivery into a customer notice and a refund claim.
Carrier tracking → customer notice → CRM / help desk → refund claim → carrier invoice- Before
- Nobody notices a shipment is late until the customer calls. Support opens the carrier portal, works out what happened, and apologizes after the fact. Refunds for missed service commitments are rarely claimed, because checking every shipment against the service it was bought under—inside the carrier’s filing window—is work nobody has time for.
- What we build
- The hub watches tracking events against the service commitment purchased for each shipment. When a delivery misses that commitment it notifies the customer with the revised expectation before they contact you, opens an owned ticket with the tracking history attached, and queues an eligible refund claim inside the carrier’s filing window. Credits are then matched back to the original shipment on the carrier invoice.
- Acceptance result
- Every shipment past its commitment produces a customer notification and an owned ticket; every claim is either filed inside the carrier’s window or recorded as ineligible with the reason; every credit received is matched to the shipment that earned it, so unclaimed and unpaid claims are both visible.
C1Connection methods
Use the access that exists.
- Carrier and aggregator APIs
- Order and inventory webhooks
- Printer services and local agents
- Address-validation services
C2Typical deliverables
Leave with an operating system.
- Carrier eligibility rules
- Rate-shopping service
- Automatic label and printer routing
- Delivery exception hub with proactive customer notices
- Service-commitment monitoring and refund claim queue
DHosting & ownership
Your infrastructure or ours.
Most automations need a secure backend to run APIs, scheduled jobs, queues, data stores, retries, and monitoring. We deploy that structure where it makes the most operational sense.
ECommon questions
The questions people ask first.
Short answers to what usually comes up before a scoping conversation. If yours is not here, ask us directly — the intro call is free.
- Can you claim refunds when a carrier misses its delivery commitment?
- The workflow can detect the miss, file inside the carrier’s window, and reconcile the credit against the invoice. Whether a given shipment is actually refundable is the carrier’s call, not ours — money-back guarantees differ by carrier and service, and several have been narrowed or suspended in recent years. The build treats ineligible as a recorded outcome with a reason, not a silent skip, so you can see what is being left on the table and why.
- How do customers hear about a delay before they call us?
- The hub watches carrier tracking events rather than waiting for a complaint. When a shipment misses its commitment or hits an exception, the customer gets the revised expectation on your terms and in your wording, and your service team gets a ticket with the tracking history already attached.
- Do we need a new system for this?
- No. The hub is a view over data your order system, shipping platform, and carrier accounts already produce. It exists so delay information stops living only in a carrier portal that the people answering customers cannot see.
- How does the automation choose a carrier?
- By your rules, not ours: it rate-shops the eligible services and selects the lowest-cost option that still meets the promised arrival date. Where no service meets the promise, it creates an exception with the rates it saw rather than quietly shipping late.
- Which carriers can you work with?
- Commonly FedEx, UPS, USPS, and DHL, plus shipping platforms such as ShipStation. What is actually available depends on your accounts, negotiated rates, and the API access each carrier grants you.
- What happens if an address changes after the label prints?
- The shipment is revalidated, the old label voided where the carrier allows it, the package re-rated, a replacement issued, and tracking kept synchronized. Each of those steps is a rule you approve rather than a default we assume.
- Can labels print automatically at the right location?
- Yes — labels can route to the printer configured for that origin or location, with the details you need on the label itself. Print acknowledgment is recorded so a failed print is visible rather than assumed.