The right work, in the right place.
A customer should not get one answer from support, another from the warehouse and a third from finance when a delivery slips or a refund is owed. Hantera_ gives commerce operations a connected place for the decisions behind the promise — and leaves the systems around it doing the job they are genuinely good at.
Where the work belongs
Commitments, availability, change, recovery and financial resolution — starting with order management.
The market rule, the return policy, the partner agreement. Versioned on their own.
ERP, warehouse, carriers, payment providers, tax services, help desk, storefronts.
Not every problem belongs to the system that met it first.
A lot of commerce software ended up owning work it never set out to own — because it was the only system close enough to the problem when someone had to solve it. It works, until the day the answer has to be right in three places at once.
The refund settled away from the sale
A returns tool decides what to pay back without the campaign the item was bought on, what was actually captured, or what shipped. The number is defensible in that tool and wrong on the order.
Availability answered by the storefront
The web shop keeps its own stock figure because nothing else can answer in real time. It sells the last unit twice, and the apology is written by someone in support.
The truth reassembled by a person
Finance, the warehouse and the help desk each hold a piece. An agent stitches them together while the customer waits — every time, by hand.
None of those systems is bad at its own job. They were simply asked to hold something that needed to stay connected to everything else.
One operating model. Three places for capability to live.
Hantera_ is not trying to replace the ERP, the warehouse system, the payment provider or the accounting software. It decides deliberately what belongs in the platform, what belongs in an app, and what should stay exactly where it is — so your own rules never have to become custom code nobody can upgrade.
Platform domains
The operational decisions that have to stay connected to each other: orders, invoices, payments and their history, available-to-promise, reservations and allocations, pricing and promotion context, tax classification, returns and refund calculation.
Apps
Returns workflow, inventory routing, payment providers, tax services, market rules and the processes that are specific to your business — installed and versioned on their own.
Connected systems
ERP and accounting, warehouse and 3PL, carriers and TMS, payment providers, tax services, help desk, ecommerce, POS and marketplaces — each still doing the job it is good at.
Keep the work together. Keep the systems in their lane.
We started where the promise is most often lost.
Order Management is the first Hantera_ platform domain: the operational lifecycle after checkout — what was promised, what can actually be delivered, what changed, and how the business recovers when it does. Inventory, returns, payments and shipping are the specialist areas within it, and each has a page of its own.
Order Management
The operational lifecycle of a commitment: what you promised, what you can deliver, what happens when it changes, and whether the money still adds up afterwards.
Order Management →Inventory & Availability
Available-to-promise, reservations, allocations, back orders and routing.
Inventory & Availability →Returns & Recovery
Claims, RMAs, inspections, recalls, refunds and replacements.
Returns & Recovery →Payments & Financial Resolution
Invoices, payment history, capture, credits and refunds.
Payments & Financial Resolution →Shipping & Consignment Tracking
Carrier events, delays, lost parcels and post-shipment compensation.
Shipping & Consignment Tracking →Keep what already works. Add what your operation actually needs.
A market that prices differently. A reseller invoiced on different terms. A return policy that exists for a reason nobody wrote down. Those are the parts that usually become custom code — and then become the reason an upgrade is postponed for two years. Apps and integrations are how they stay maintainable instead.
Integrations
ERP, ecommerce, POS, warehouse, logistics, help desk, tax and payment systems keep their authority — and stop disagreeing about what happened. No replatforming project.
Integrations →Apps & extensibility
Package a capability as an app instead of a patch: installed, versioned and upgraded on its own, whether it is a tax integration or one market's return rule.
Apps & Extensibility →App marketplace
Browse what you can install today — from Hantera_, from the vendors you already use, and in time from partners building on the platform.
App Marketplace →Proof, not promises.
Didriksons replaced their ERP and their commerce stack in the same quarter, with Hantera_ as the hub every other system met in — eight markets, four fulfilment locations, and a go-live on the date they originally set.
Show us where the work is landing in the wrong place.
Bring the systems, the markets and the one process everyone says cannot be standardised. We’ll show you what Hantera_ should own, what should stay exactly where it is, and roughly what it takes to get there.