Nothing to build on your side
We connect your carrier accounts and create your clients' accounts before go-live. No code to write, no technical resource to pull in.
Warehouses and 3PL providers
Ship for every client
as fast as you ship
for one
on your own carrier contracts
Rules pick the carrier, customs documents come out with the label, statuses go back to your client's store. Your team works in our interface, or your WMS calls our API. Either way, there is nothing to build on your side and no one to wait for.
Your contracts,
your carriers
your carriers
Not a line of code,
now or later
now or later
Two-hour response,
in business hours
in business hours
GDPR, a signed
processing agreement
processing agreement
You and your clients
What ParcelRush changes for you and for your clients
You are not selling labels to your clients. You are selling them the certainty that their parcels leave on time, fast, and without friction.
For your operation
One account for the whole dock
Your operators work in a single tool, however many clients you ship for. One sender address per client, rules that decide the carrier, and the day's orders handled in batches instead of one at a time.
For your clients
A parcel that goes out in their name
The label and the documents carry their sender identity, the carrier suits each destination, and statuses flow back to their store. They keep the relationship with the end customer, you keep control of the dock.
Interface mode
One fast interface to centralise everything
Built for warehouses with no in-house WMS, or that would rather not touch the one they have. Your operators run shipping from our interface.
See the platform in detail
Your clients' stores, connected
Shopify, WooCommerce and Squarespace import natively, and your clients' orders arrive on their own. For a store on another platform, CSV import takes over.
Everything from the browser
Client accounts, routing rules and batch processing, with no install and no dedicated workstation on the dock.
A dock that runs on its own
Your operators are self-sufficient after a short walkthrough, and a new hire ships like everyone else on day one.
API mode
Your cut-off
does not move even when volume doubles
ParcelRush is the TMS your WMS calls. A WMS handles stock and picking, it was never built to follow six carriers changing their APIs. Your system sends the order and gets back the label, the customs documents, the statuses and the cost of the shipment. Nothing goes through your WMS vendor, and your WMS keeps updating your client's store the way it does today, whatever platform that store runs on.
See the integrations
What your WMS drives
- Create the shipmentOne request, one label. Returned as PDF, ZPL or PNG depending on your printers.
- Process in batchesPush several shipments in one request and get the labels back together.
- Pick the sender and the siteName, on every call, the client the parcel goes out for and the warehouse it leaves from.
- The cost of each shipmentThe shipment amount, tied to the client, so you can price your re-invoicing without manual reconciliation.
- Apply your rulesLet the routing rules choose the carrier, or force it from your WMS.
- Automatic HS codesA customs code is suggested for every item, so nobody has to look it up.
- Customs documentsCN22, CN23 and the commercial invoice produced with the label, with nothing re-keyed.
- Book a pickupSchedule the carrier collection and get the handover note back.
- Issue the paperworkProduce the picking list and the packing slip tied to the order.
- Track the shipmentGet the tracking number and then the statuses, which your WMS passes on to your client's store.
- Receive the eventsParcelRush pushes status changes to your system, with no polling loop on your side.
- Generate a returnProduce a return label tied to the original order.
The exact endpoints and the payload format are agreed with your technical team during scoping.
Reliability and volume
What holds when
volume climbs
Sized for your peaks
Batch processing is calibrated on your busiest days, not your yearly average. A volume that doubles does not move your cut-off.
Dedicated infrastructure
Above a certain volume, we isolate your operation on servers reserved for your activity alone.
Changes absorbed
When a carrier changes its API, our team rewrites the code. Your teams never hear about it.
Warned before your clients are
If something breaks on our side, an alert is pushed to the dashboard. You do not find out from your clients.
Your carrier rates
Your margin
stays yours
You buy transport at your own rates, on your own account numbers. We do not resell transport, and we take nothing from the gap between what you pay and what you invoice your clients.
When your WMS calls us, it also gets the cost of each shipment, tied to the client that generated it, so nobody has to reconcile lines by hand.
Getting started
From the first call
to the first parcel
- First callThirty minutes to understand your organisation and your tools.01
- Written proposalPlanned setup, pricing, go-live date.02
- ConfigurationCarriers connected, or an integration built to order.03
- Go-liveA first batch in real conditions, then the whole dock.04
Talk to our team
Tell us about
your warehouse
Monthly volume, number of clients, carriers already in place, management system in use. With that, we reply within one business day and set up a first call. The costed proposal comes next, once we understand your setup.
The dock does not stop
Configuration runs alongside your operation. You switch a pilot batch first, then the rest.
Your clients never notice
Parcels keep going out in their name, with their tracking, throughout the go-live.
You set the calendar
Go-live follows your activity, not ours. You pick the week, and nothing starts until your operation signs off.
FAQ
Questions from warehouses
and 3PL providers
Does ParcelRush replace our WMS?
No. ParcelRush is shipping software, not warehouse management software. Your WMS keeps stock, locations and picking. ParcelRush takes the transport layer: carrier selection, labels, customs documents and tracking. The two work together.
Can we ship in our clients' names?
Yes. You register one sender address per client and select it on the order. The label and the documents go out in that client's name, from your account.
Do we have to change our carrier contracts?
No. You keep your accounts and the rates you negotiated. We handle the connection with each carrier during go-live, and you can add a carrier later.
Does ParcelRush connect to our WMS or our ERP?
Yes, through our API. Your WMS creates the shipment, buys the label and gets the tracking number back without your operators changing screens. We look at the connection during scoping and tell you what is feasible before sending you a proposal.
Who builds the integration to our system?
We do. Development is handled by our team, against a specification agreed with your technical team. You sign the result off on a test environment before anything goes to production.
How do we know whether we are an interface case or an API case?
If you have no WMS, or would rather not touch the one you have, interface mode is the fastest to set up. If your operators already work in a WMS you do not want to replace, it is API mode. Scoping settles it, and we will tell you plainly if your volume does not justify a development project.
How long does a label take to come back?
That depends mostly on the carrier's API rather than on us: around half a second with the fastest, five to six seconds with the slowest. It is worth knowing when you arbitrate between two carriers on the same flow, and we give you the orders of magnitude carrier by carrier during scoping.
Can you isolate our operation on dedicated infrastructure?
Above a certain volume, yes: we dedicate servers to your activity alone, so your throughput does not depend on other accounts. The threshold and the terms are set during scoping.
How is pricing set for a warehouse?
Case by case. Volume, deployment mode and the setup involved are never the same from one warehouse to the next, so the price is built with you during scoping and written into the proposal.
Is there a service level commitment?
Support runs Monday to Friday, 9.00 to 18.00, with the person who ran your go-live, and a two-hour response. Contractual response times are written into the proposal before you sign: they depend on your volume and on how critical your operation is, so we would rather set them with you than post a number at random.
How do we answer our clients on GDPR?
Your client is the controller, you are their processor, and ParcelRush becomes a sub-processor. We accept being named as such in your contract, and we provide on request the Article 28 data processing agreement, the list of sub-processors, the hosting location and the retention periods, which is what an audit annex needs. The detail is on our compliance page.
A setup described,
priced and dated
Tell us about your warehouse. A person replies within one business day, not a form.
Named contactIntegration maintained by us