Many forwarders keep CargoWise as the system of record and build their own layer for what it does poorly: quoting, customer portals, reporting, document automation, and AI agents, connected through CargoWise's integration interfaces. You get the capabilities that set you apart without a full migration, and the pieces carry over if you later replace the core.
Why this option is growing
AI has lowered the cost of building software, and forwarders are using that to build application layers matched to their own workflows rather than waiting for a vendor to build them (The Loadstar). The core system keeps doing what it's good at: transactions, accounting, and customs. Your layer does what makes you different.
Good candidates to build, and what to leave in the core
| Build in your own layer | Usually keep in the core |
|---|---|
| Quoting and rate management | Job and shipment records |
| Customer portals and notifications | Customs filing |
| Reporting, analytics, and a data warehouse | Billing and the general ledger |
| Document reading and automation | Statutory documents |
| AI agents for email, exceptions, and milestones | Master data |
Design it so it survives a replacement
- Own the data layer. Replicate the data you need into a warehouse you control. Reporting, AI, and any future migration all start there.
- Keep business logic in your layer. Pricing rules, margin rules, and customer-specific logic shouldn't live only in CargoWise configuration.
- Use clean interfaces. Connect through supported integration interfaces, so replacing the core means re-pointing connections rather than rebuilding everything.
Watch the cost of integrations
Under per-job pricing, how your layer creates or updates records in CargoWise can affect your bill. Design integrations so they don't create unnecessary jobs. One forwarder we work with consolidated warehouse receipts into a single shipment for exactly this reason. Our Value Pack guide explains how pricing works.
When building on top stops making sense
- Most of your daily work happens in your own layer and the core is mainly a ledger you pay per job for.
- Integration upkeep costs more than the core saves.
- The core's design blocks a process change you need.
At that point, replacing the core is the next step, and the layer you've built becomes the starting point for it. See how to migrate off CargoWise.
Common questions
Is building on top of CargoWise allowed?
CargoWise provides integration interfaces for connecting other systems, and many forwarders and software providers use them. Check your agreement for any terms that apply to your setup.
What should we build first?
The piece with the clearest payback and the fewest dependencies. Quoting, customer portals, and reporting are common first projects.
Will our layer work with a different core system later?
Yes, if it is designed that way: your own data layer, your own business logic, and clean interfaces. Then a replacement means re-pointing integrations rather than rebuilding.