Pricing, as plainly as we can put it
One service on this page has fully published rates, because its scope is standard enough to price honestly in public. The rest are priced on scope after a short audit – and this page explains exactly what drives those numbers, so your quote is never a mystery.
Truck dispatch is priced in the open: a flat $250–$350 per truck per week, or 5–10% of linehaul – your choice, with a free trial week and no forced dispatch. Every other service is quoted as a fixed scope or a monthly engagement after a short audit, because the honest price depends on your volume: ticket counts, catalog size, feed errors, sites, and team size. You always receive the number in writing, with what is and is not included, before any work starts.
Truck dispatching: the full price, in public
| Model | Rate | Best for |
|---|---|---|
| Flat weekly | $250–$350 per truck, per week | Steady lanes and predictable weeks; you keep every dollar above the flat rate |
| Percentage | 5–10% of linehaul | Variable volume; the fee scales with what the truck actually earns |
| Trial | First week free | Judge the work before judging the price |
No setup fee, no long-term contract, and no forced dispatch under either model. The percentage-vs-flat break-even math is worked through in our guide.
How the other services are priced
Fixed-scope projects
For work with a natural end: Merchant Center diagnostics and remediation, catalog cleanup and migration, help center builds. Audited first, then one fixed price for the agreed scope – paid against deliverables, not hours.
Monthly managed services
For ongoing operations: e-commerce support, SaaS support, WordPress care. A monthly engagement scaled to your volume and coverage hours, reported monthly, with scope adjustable as volumes change.
Fractional operations
Senior operations leadership in a defined weekly block, for businesses that have outgrown improvisation but not yet a full-time hire. Priced on the block and the outcomes agreed, not on attendance.
What actually drives your quote
- Support: weekly ticket volume, channels covered (chat, email, phone), coverage hours up to 24/7, and how many product lines agents must master
- Merchant Center: feed size, number and type of errors, and whether the work is data-only or includes a suspension appeal
- Catalog: SKU count, variant complexity, and the condition of the data being cleaned or moved
- WordPress: number of sites, plugin and theme complexity, and whether e-commerce is involved
- Operations: team size, number of workflows in scope, and reporting depth
- Every service: the state things are in today – fixing a neglected operation costs more than running a healthy one, and the audit tells us which you have
Because a support queue of 80 tickets a week and one of 800 are different jobs, and a published "range" wide enough to cover both would tell you nothing. A short scoping conversation produces a real number for your actual volume – that is the figure worth having.
- Every quote in writing, with inclusions and exclusions stated
- No work starts before you approve the number
- Scope changes are priced and agreed before they are done, never after
- Your accounts, data, and licenses stay in your name
Get the real number for your volume.
Tell us the service and the scale – tickets per week, SKUs, trucks, sites. The reply is a scoped quote, not a sales sequence.
Related: Our process · Fractional vs full-time cost comparison · Cost to outsource e-commerce support