In short: Ecommerce delivery management software lets your own team set delivery options, carriers, and pricing rules without writing code. Flügger now runs checkout across five B2B markets with zero developer hours per change, and Embacollage runs freight and booking inside Microsoft Dynamics 365 Business Central. The controls sit with the people who run the operation.
The fastest delivery teams share one trait: they can change their own rules. A shipping price, a new carrier, a label that once needed a second system, all handled by the people who run the operation rather than a developer.
Two recent nShift customers moved those controls in-house. Flügger, a Danish paint manufacturer, now configures checkout across five B2B markets without touching code. Embacollage, a European packaging and fulfilment provider, runs freight, picking and booking from inside one system. The products differ and so do the problems, but the underlying move is the same: they put the day-to-day controls in the hands of the people who run the operation.
What ecommerce delivery management software should let you change yourself
Good ecommerce delivery management software lets the operations team change the rules that change most often. That means delivery options, carrier choice, and pricing logic by cart value, weight, and location, all editable in an interface rather than a codebase. When a carrier changes a rule or a new market opens, can your team make the change that day, or does it wait on a developer?
These are the changes that recur in any growing operation: a carrier updates its surcharges, a new market needs its own delivery methods, a heavy product line needs weight-based pricing, a rural postcode needs express switched off. None of them are complex on their own. The cost is in how they are handled. When each one needs code, small changes stack up behind larger projects, and the team that understands the delivery promise is the team least able to adjust it.
Changes a team should make without code
- A carrier updates its surcharges
- A new market needs its own delivery methods
- Weight-based pricing for a heavy product line
- Express switched off for rural postcodes
For Flügger, those changes used to go to developers. Now its own team makes them.
Flügger: checkout rules, set by the team that runs them

Flügger makes paint and coatings, employs around 1,700 people, and runs factories in four countries. It sells to professional painters through B2B webshops in five markets. Its old stack ran 18 webshops on an Episerver monolith, with a separate system handling shipping and labels. Adjusting a shipping price, a drop point, or a delivery rule meant development work, even for small changes. In physical stores, staff finished an order in the ERP, then logged into a second system to print the label.
The team weighed building checkout themselves and decided against it.
"We considered building checkout ourselves. Technically it's not that hard, but we thought about the maintenance: we'd have to code against every carrier. When a carrier makes changes, we probably wouldn't be the first to know. We'd always be behind."
Thomas Lauenborg, Product Owner E-commerce, Flügger
In November 2025, Flügger went live with nShift Checkout across all five B2B sites in Denmark, Sweden, Norway, Poland, and Iceland. Now the team sets delivery rules by cart value, weight, and postal code directly in the interface. Express delivery switches off automatically for rural areas. Shipping prices recalculate as customers add heavy items. Every change is testable in a live environment before it reaches the shop. Across the five markets, checkout offers PUDO points alongside GLS, PostNord, and DHL from the nShift carrier network, keeping the delivery choice focused.
The results show up in three numbers from go-live: zero customer-reported errors, five B2B webshops live, and zero developer hours per checkout change.
"Customers don't call saying they can't complete their order. It just runs through."
Thomas Lauenborg, Product Owner E-commerce, Flügger
One known edge case around invalid postal codes is being resolved.
Zero
customer-reported errors since go-live
Flügger B2B checkout, live November 2025
Five
B2B webshops live on nShift Checkout
Denmark, Sweden, Norway, Poland, Iceland
Zero
developer hours per checkout change
Rules configured by the team, in-interface
The change the team feels most is ownership.
"It works fabulously well. It's really easy and intuitive to work with. It's a satisfaction to sit with it ourselves. It's not in a black box. We set the requirements, and we can do it ourselves."
Thomas Lauenborg, Product Owner E-commerce, Flügger
The shift came as part of a wider rebuild. When Flügger moved its e-commerce stack to a composable architecture, checkout was one piece it chose to buy rather than build, precisely so the team would not spend its time maintaining carrier connections. That decision now pays off every time a market needs a different rule. The same change can ship in Denmark and Poland without five separate development tickets, and the live-test environment means the team can see exactly how a new rule behaves before a customer ever meets it.
Flügger is now extending the same checkout to its B2C sites, and using nShift Companion, the AI assistant built into Checkout, to build custom operational logic. One current project calculates the number of pallets a shipment needs by weight and routes that count to the fulfilment centre. The team is also exploring customer-specific freight pricing and a scan-and-go option using QR codes in its physical stores.
Embacollage: freight, picking and booking in one Business Central flow

The same principle holds away from the storefront, on the warehouse floor.
Embacollage supplies packaging, point-of-sale and shipping materials across Europe, with warehousing, distribution, inventory management, and webshops for more than 220 retail brands. As its logistics grew more involved, its freight and warehouse work was spread across several systems. Picking and packing ran off printed pick lists. Booking a shipment meant moving between tools. The company wanted employees to handle more of the flow in one place, and customers to see clearer freight costs before an order moved.
Working with partners Obtain Group and XtensionIT, Embacollage used Shipment Connector to bring freight and logistics functions from nShift Ship directly into Microsoft Dynamics 365 Business Central. That ERP integration connected order handling, warehouse processes, shipment booking, and freight calculation into one flow. Staff now move from picking and packing with a Tasklet Factory scanner through to booking and freight calculation without leaving Business Central. A sales freight calculation layer prices freight from Embacollage's own carrier agreements and criteria such as weight and location.
The freight calculation layer is the part that earns its keep. Because prices come from Embacollage's own carrier agreements and from criteria such as weight and location, the number a customer sees reflects what the shipment actually costs to move. That keeps margin visible at the point of sale rather than reconciled after the fact, and it removes the guesswork that creeps in when freight is priced by hand.
The outcome is a more connected freight process: reduced manual freight steps, clear shipping cost visibility, and better transport cost control. Freight calculation, label management, picking, and track-and-trace now run through one digital workflow. Customers see clearer freight pricing before checkout, and Embacollage gets stronger margin visibility and tighter control over transport costs, with continuously updated track-and-trace information that supports proactive customer communication.
The common thread: the controls live with the operator
The two stories run on the same operating choice: whoever runs the operation holds the controls that change most often.
For Flügger, the controls are at the checkout: delivery areas, express availability, methods, and weight-based pricing, all managed without custom development, and one less system to log into when a store prints a label. For Embacollage, the controls are at the warehouse: freight calculation, booking, and label management, all inside the ERP the team already works in. In both, the work that used to require a second system or an outside developer now happens where the order already lives.
That gives you a sharper question to ask when you evaluate a delivery management system: who has to touch it to change a rule? The closer that person sits to the operation, the faster you move when a carrier shifts, a market opens, or a price needs to change. Both companies built that into their stack with the modular nShift platform, adopting the piece that fit the job, from checkout to the warehouse.
Put the controls where the work happens
The best delivery setups give the team a number worth repeating. Flügger has zero developer hours per checkout change. Embacollage has freight and fulfilment in one flow. Bring us the rule, the market, or the process you want to run yourself, and we will show you where nShift fits across your checkout, carriers, and warehouse. Book a demo and we will start with the one you most want to control.
FAQ
Can you change shipping rules without a developer?
Does delivery management software work with an ERP like Business Central?
What is the difference between checkout-side and warehouse-side control?
About the author
Thomas Bailey
Thomas plays a key role in shaping how new features and platform improvements deliver real value to customers. With a background spanning product, tech, and go-to-market strategy, he brings a pragmatic view of what innovation looks like in practice and how to make delivery experiences work harder for your business.