Labels cannot be voided for refund
Unused labels that sat for longer than the carrier's refund window, so ShipStation can mark them void internally but cannot recover the cost from USPS or UPS.
Void workflow run inside the refund window
Running on ShipStation?
ShipStation is the backbone of a lot of 3PL and in-house shipping floors, and when it misbehaves the entire fulfilment day slows down. Labels that will not void, carrier rate cards that disagree between the quote and the actual purchase, a Shopify sync that is nine hours behind, or an automation that keeps assigning the wrong service to international orders. We work through the store connections, the automation rules and the carrier accounts until the orders flow again.
What it is
ShipStation is a multi-carrier shipping and order management platform founded in 2011 in Austin, Texas, and acquired by Auctane. It sits between an online store (or several), a warehouse floor and a group of shipping carriers, pulling orders in, applying business rules, rating them against negotiated carrier accounts, printing labels and feeding tracking back to the stores.
The platform integrates with Shopify, Amazon, eBay, Walmart, Etsy, Magento, BigCommerce, WooCommerce and most mainstream order sources, and supports USPS, UPS, FedEx, DHL, OnTrac, Canada Post and a long tail of regional carriers in the US and internationally. The work that reaches us is typically where ShipStation meets the real world, specifically an expired FedEx contract, a customs field not being populated, a batch-sync lag that makes end-of-day scan forms incomplete, or an automation rule that quietly started picking the wrong service.
The honest version
No technology is all upside. This is where ShipStation earns its place and where it tends to cause trouble.
Sound familiar?
The ShipStation problems that bring people to us, and what you have once each one is fixed.
Unused labels that sat for longer than the carrier's refund window, so ShipStation can mark them void internally but cannot recover the cost from USPS or UPS.
Void workflow run inside the refund window
A dimensional weight that was not set correctly, a zone that shifted between quote and purchase, or a fuel surcharge update in the middle of the batch, so the actual label cost is higher than the shipping charged.
Dim weight and surcharge handling verified
Shopify is rate limiting the ShipStation connection, or the shop has grown past the plan's leaky bucket, so orders are reaching the shipping queue hours after they are placed.
Sync keeping up in real time
A FedEx or UPS negotiated contract that lapsed without being re-imported, so every label since the expiry has been rated at list price, costing meaningful money on every outbound package.
Negotiated rates reinstated and backfilled
An automation rule that filters on inventory location overriding a combined-order rule, so a customer ends up with two shipments for one order and two tracking emails.
Rule order corrected and combined shipping working
A product catalog that is missing HS codes or country of origin on some SKUs, so international labels either print without compliance data or refuse to print at all.
HS codes complete and validated on save
Scripts or 3PL tooling still consuming the ShipStation v1 API with a deprecation date on the calendar and no equivalent call yet mapped to v2.
Integrations migrated to v2 ahead of the deadline
What we do
Reach out when a single automation is picking the wrong service, or hand us the whole shipping operation across brands.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Each carrier has a refund window, typically 28 days for USPS and tighter for FedEx and UPS. Labels that were printed but not scanned must be voided inside that window or the cost sticks. We set up a weekly unused-label report that fires an auto-void for anything approaching the carrier limit, so unused labels stop silently becoming sunk costs.
Three usual causes. Dimensional weight was not configured on the package type, so the real billed weight is higher than the quote. The zone moved because the ship-from changed. Or a fuel surcharge updated between the rate call and the purchase. We check the package profile, confirm dim weight is applied, and compare recent labels where the delta appeared to isolate which of the three is biting.
Usually Shopify is rate limiting ShipStation because the store has grown past its API bucket, or ShipStation itself is backed up. We check the sync log on both sides, raise the Shopify plan or spread the sync load if needed, and in a 3PL with many connected stores we rework the architecture so one noisy brand does not starve the others.
Yes. The data worth moving is the carrier accounts, the automation rules and the historical label data. We rebuild the rules on the new platform, verify rate parity against real recent orders rather than demo ones, and run both systems in parallel through a cutover period before the old one is retired.
The contract on the carrier side expired, the carrier key needs reauthorizing after a carrier portal change, or the account in ShipStation is pointing at an old contract number. We re-import the current negotiated rate card, confirm the next few labels bill correctly, and set an alert for 60 days before the contract next expires.
The estimate is free. Describe the shipping floor, the stores feeding it, the carriers in use and the problem you are hitting, and we respond with a price before we touch an automation rule.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: