Supply Chain & Logistics
nShift
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by nShift Group AB · www.nshift.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
nShift at a glance
- Vendor
- nShift Group AB
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates nShift 3/5, the mean of 6 judges. nShift Group AB is judged as a multi-carrier delivery platform running behind the WMS and ERP it connects to, not a stock or warehouse system. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
nShift Group AB is judged as a multi-carrier delivery platform running behind the WMS and ERP it connects to, not a stock or warehouse system. Shipping and returns is the strongest area, built on rule-based carrier selection priced against the buyer's rate card or carrier API, customs documents with HS codes, branded tracking and a self-service returns portal with per-item reason and condition codes. Freight and transport scores 7 to 8, the lower marks reflecting no public information on tenders or eCMR-style documents, while integration and automation holds at 7 on 450+ maintained connectors with a REST API and an on-prem XML option. Weaknesses are structural: sovereignty records the floor and inventory control 0 to 2; no public information appears on hosting, subprocessors or certifications, and the stock record lives in the connected systems. Warehouse operations splits 2 to 4, higher marks crediting the packing-station label flow and returns scan, the low mark resting on that thin slice. The returns product publishes three tiers — Essential, Professional, Premium — with no figures.
Speaks for it
- Shipping and returns is documented end to end — rule-based carrier selection on the buyer's imported rate card or carrier-API contracted rates, customs documents with HS codes and electronic submissions, branded tracking, and a self-service returns portal with per-item reason and condition codes.
- Freight covers road, sea and air with consolidation, pallet-level goods detail, inbound transport where suppliers book under the buyer's carrier contracts, spot prices, and a carrier-invoice audit that claims back overcharges.
- 450+ integrations are certified and actively maintained, naming real systems — Microsoft Dynamics, SAP, NetSuite and Visma on ERP; Shopify, Magento and others on shops; WMS platforms including Blue Yonder, Ongoing and Infor WMS — with a REST API, an on-prem XML option and EDI connectivity.
- Pack confirmation triggers the carrier booking and labels print at the packing station in ZPL or PDF, with carrier status flowing back into the WMS.
- Emissions per shipment are calculated with an NTM-based method for European shipments, broken down by carrier, route and business unit, and feed sustainability reporting.
Held against it
- The stock record lives in the WMS or ERP it connects to, with no public information on stock movements, bin locations, batches, serial numbers or reorder points (inventory control 0–2).
- No public information appears on hosting location, subprocessors, data processing agreements or security certifications, though recipient addresses flow to every carrier booked (sovereignty 0).
- We found no public information on webhooks, API rate limits and versioning, or a documented export of order and shipment history when the contract ends.
- We found no public information on tenders compared across many carriers, on eCMR or digital delivery notes, or on dock and yard booking, which held freight and transport at 7 to 8.
- The captured pages give different figures for connected carriers — over 1,000 in places, 240+ already connected on the transport page — so verify coverage for your own carriers.
Best for
- You ship high parcel volumes across many carriers and want automatic carrier and service selection priced on your own negotiated rates, with customs paperwork and branded tracking in one flow.
- You run a heavy returns operation and want a branded self-service portal with rule-based fees and windows per market, reason and condition codes per item, and refunds that trigger automatically into your ERP or shop.
- You already run a WMS or ERP — Microsoft Dynamics, SAP, NetSuite, Visma, Blue Yonder and Ongoing are among the 450+ integrations — and want a delivery layer that runs behind it rather than replacing it.
- You book road, sea and air freight and want carrier invoices audited against contracted rates plus per-shipment emissions on a named method feeding sustainability reporting.
Avoid if
- You need stock control — bin locations, batches, serial numbers, reorder points — inside the shipping tool itself; the captured pages place the stock record in the WMS or ERP it connects to.
- You need the product to run your warehouse floor — goods receipt, putaway, scanner-guided picking — rather than sit behind an existing WMS, which is how the pages position it.
- You must have hosting location, the subprocessor list, a data processing agreement or security certifications documented before signing; the judges found no public information on these and advise demanding them in writing.
- Your signing checklist requires webhooks, published API rate limits and versioning, or a documented end-of-contract export of order and shipment history — the judges flagged each of these as unanswered here.
The scores
| Criterion | Panel median |
|---|---|
| Inventory & stock control | 0.5 of 5 |
| Warehouse operations: receiving, picking & packing | 2 of 5 |
| Multi-carrier shipping & returns | 4.5 of 5 |
| Freight & transport management | 4 of 5 |
| Integrations, automation & exit | 3.5 of 5 |
Inventory & stock control
Show reasoningHide reasoning
How this is scored
Whether the stock figure can be trusted: every goods receipt, sale, transfer, return and correction booked as a movement, stock per location and channel, batches, serial numbers and best-before dates where the goods need them, reorder points and purchase orders, and stock synchronised to every sales channel so nothing is oversold.
0 — No stock keeping; quantities live in the shop or in a spreadsheet.
3 — A stock number per product that can be edited by hand, with no movement history, no locations and no link to purchasing.
5 — Stock per product and warehouse updated by orders and goods receipts, synchronised to the connected sales channels, with low-stock alerts and purchase orders to suppliers.
8 — Every movement booked with a reason and a user, stock per bin location, batches, serial numbers and expiry dates tracked, stocktaking (cycle or annual) supported, bundles and kits resolved to components, and reorder suggestions from sales history.
10 — The stock record is an audit-proof ledger: complete movement history exportable, inventory valuation method stated (FIFO, average cost), multi-warehouse and multi-entity stock with transfers in transit, demand forecasting documented, and the stock figure reconciled across every channel in near real time.
The E-Commerce Operations Lead
The captured pages describe a multi-carrier shipping and delivery platform whose documented modules are Core booking, Cost, Collaborate, Emissions and Report, with the stock record living in the WMS and ERP systems it connects to. The only stock-adjacent evidence is the returns flow, where restock status stays visible after the warehouse scan; we found no public information on stock figures per channel, movement history, bin locations, batches or reorder points. I would keep my inventory ledger in the WMS and let this tool carry the parcels. 1 4 5
The Warehouse Manager
The captured pages describe a delivery management platform — checkout, shipping, tracking, returns, invoice audit — with stock figures living in the WMS and ERP it connects to, and I found no public information on nShift itself booking stock movements, bin locations, batches, serial numbers or best-before dates. The nearest touch is restock status staying visible in the returns scan tool, which is returns handling, not stock control. 1 2 4
The Transport Planner
The captured pages describe a delivery management platform running from checkout through tracking, returns and invoice audit, and the only stock-adjacent fact is that restock status of returned goods stays visible alongside the returns scan tool. I found no public information on stock figures, movement history, bin locations, batches, serial numbers or reorder points. 1 4
The Fulfilment Provider
The captured pages describe nShift as a multi-carrier delivery platform that runs behind WMS systems, with orders flowing in from the WMS or ERP — the stock itself stays in those systems, not here. The only stock-adjacent item is restock visibility on processed returns. We found no public information on stock movements, bin-level stock, batches, serials or stock synchronised across channels. 1 2 4
The IT & Integration Lead
nShift is a delivery-management layer rather than a stock system: its own pages describe it running invisibly behind WMS platforms, so the stock record lives in the warehouse system it connects to. The only stock-adjacent facts are a returns scan tool showing item-level data with restock status visible. We found no public information on stock movements, bin-level stock, batches, serial numbers, reorder points or channel synchronisation. 2 4 6
The Skeptic
The captured pages describe a multi-carrier delivery platform that runs behind other people's systems — orders flow from the WMS, shipping data passes back, and the stock figures live in whatever ERP or WMS the customer connects. We found no public information on stock movements, bin locations, batches, serial numbers, reorder points or stock synchronisation to sales channels. Buy it for shipping; we found nothing here that would make me trust it as a stock ledger. 1 2 3
Warehouse operations: receiving, picking & packing
Show reasoningHide reasoning
How this is scored
The physical work in the warehouse: goods receipt against a purchase order, putaway to bin locations, picking strategies (single order, batch, wave, zone), scanner and mobile app guidance, packing with checks, and the performance figures a warehouse lead runs the shift by.
0 — No warehouse process support; staff print the order and walk.
3 — A pick list or packing slip printed per order, with no bin locations, no scanning and no check that the right item went into the box.
5 — Bin locations, goods receipt against purchase orders, pick lists sorted by route, and barcode scanning on a phone or scanner to confirm picks and packs.
8 — Several picking strategies (batch, wave, multi-order trolley), putaway suggestions, packing with weight or scan verification, handheld scanner support named, and pick, pack and error rates reported per user and shift.
10 — A full WMS documented end to end: slotting and replenishment, cross-docking, multi-client operation for 3PLs with client billing, integration with automation (conveyors, pick-to-light, AutoStore or similar) named, and offline-tolerant mobile apps with an audit trail of every scan.
The E-Commerce Operations Lead
Labels and any customs documents print at the packing station in ZPL or PDF once pack confirmation triggers the carrier booking, and staff can enter or scan the order ID in the WMS to print — exactly the packing bench I run. The picking, putaway and goods-receipt work is documented as living in the WMS platforms behind it (Blue Yonder, Ongoing, Infor WMS and others), and I found no public information on bin locations, picking strategies or scan-verified picks inside nShift itself. The returns scan tool with item-level data and return pre-notification will earn its keep in January. 2 4 6
The Warehouse Manager
nShift meets the warehouse at the pack bench: scanning or keying the order ID prints the label and customs documents in ZPL or PDF at the packing station, pack confirmation triggers the carrier booking under the shipping rules, and carrier status flows back into the WMS — the vendor even positions it as running invisibly behind the WMS's own interface. I found no public information on goods receipt against a purchase order, putaway to bins, or scanner-guided picking; orders flowing into pick, pack and print workflows is the only mention of the pick side. A Monday temp could ship from this, but the warehouse work itself is another system's job on this evidence. 2 6 4
The Transport Planner
Orders flow into pick, pack and print workflows, labels and customs documents print at the packing station in ZPL or PDF when the order ID is entered or scanned, and a scan tool handles item-level returns data. I found no public information on bin locations, goods receipt against purchase orders or picking strategies — the pages position the product as running behind existing WMS platforms rather than being one. 2 6 4
The Fulfilment Provider
For my floor this is a shipping layer bolted to the client's WMS, not a warehouse system: labels print at the packing station by entering or scanning the order ID, pack confirmation fires the carrier booking, and an item-level scan tool handles inbound returns with pre-notification and restock status. We found no public information on bin locations, putaway, picking strategies, goods receipt against purchase orders, or per-user pick and error rates. 2 4 6
The IT & Integration Lead
Orders flow into pick, pack and print workflows in the connected WMS, labels print at the packing station in ZPL or PDF when the order ID is entered or scanned, and pack confirmation triggers the carrier booking, with the returns module adding a warehouse scan tool and return pre-notification. We found no public information on putaway, bin locations or picking strategies; those live in the WMS nShift sits behind. 2 4 6
The Skeptic
Receiving, putaway and picking are the WMS's job in this architecture — nShift's own pages say it runs "invisibly" behind large WMS sites and that pack confirmation triggers the carrier booking. What nShift documents on the floor itself is a packing-station label flow in ZPL or PDF set off by entering or scanning the order ID, plus an item-level scan tool for returns with pre-notification to the warehouse. We found no public information on bin locations, goods receipt or picking strategies, so the score rests on that thin slice. 2 4 6
Multi-carrier shipping & returns
Show reasoningHide reasoning
How this is scored
Getting parcels out and back: carriers connected, label creation in bulk, rules that pick the carrier and service, customs documents for non-EU destinations, tracking and the notifications the recipient sees, a returns portal, and whether the customer uses its own carrier contracts or buys labels through the vendor.
0 — No shipping features; labels come from each carrier's own portal.
3 — Labels for one or two carriers created one by one, with no rules, no tracking for the recipient and no returns handling.
5 — Several carriers connected with bulk label printing, a choice between own carrier contracts and vendor rates, tracking numbers written back to the shop, and a basic returns label flow.
8 — Shipping rules by weight, destination, value and channel choose carrier and service automatically, customs documents (CN22/CN23, commercial invoice, EORI, HS codes) generated, branded tracking pages and notifications, a self-service returns portal with reasons, and pickup points supported.
10 — Shipping runs without a person: rate comparison across carriers at label time, own contracts for every connected carrier, delivery promise and checkout options from live carrier data, returns with refund or exchange triggered on receipt, and carrier performance and cost reported per lane.
The E-Commerce Operations Lead
This is the heart of it: 1,000+ carriers across roughly 190 countries plus 70+ pickup-point networks, shipping rules that choose carrier and service on price, lead time, cut-off or carbon, real-time rate evaluation on my own negotiated rates, and customs paperwork with HS codes, commercial invoices and electronic submissions — Switzerland without retyping. Tracking is branded and consolidated into one feed across channels, and the returns portal is the full January fix: branded, rule-based fees and windows per market, reason and condition codes per SKU, exchanges, refunds firing automatically into the ERP or shop, with the WMS able to process the return on the warehouse scan. It sits just under the top step because I found no public statement that own carrier contracts apply to every one of the thousand connected carriers. 1 2 3 4 5 7
The Warehouse Manager
Shipping rules pick the carrier and service automatically by cost, service level, destination, cut-off and carbon footprint, comparing eligible services on the customer's own negotiated rates with surcharges included, and customs documents with HS codes, commercial invoices and electronic submissions are generated across a thousand-plus carriers. Returns are a real self-service flow — branded portal, reason and condition codes per SKU, rule-based fees and windows per market, exchanges, refunds firing automatically into ERP or the shop, and channels from courier pickup and lockers to QR-code and label-free, with seventy-plus pickup-point networks. I stopped just short of full marks because the pages do not state that own carrier contracts apply to every connected carrier, though imported rate cards and contracted rates via carrier APIs are clearly supported. 3 4 7 2
The Transport Planner
Real-time carrier rates and rule logic pick the carrier and service per order, customs papers with HS codes, commercial invoices and electronic submissions are generated, tracking is branded and consolidated, and the self-service returns portal covers reason and condition codes per item, exchanges, automated refunds and pickup points across 70+ PUDO networks. Rate comparison at label time, own rate cards via import or carrier API, and spend reported by carrier and route are all documented, which puts this close to the top level. 3 4 7 2
The Fulfilment Provider
This is the product's core and it is strong: rules choose carrier and service on price, lead time, cut-off and carbon; real-time rate evaluation prices on my negotiated rate card or the carrier's contracted rates; customs documents with HS codes and electronic submissions generate automatically; tracking consolidates into branded pages; and the returns portal carries per-market fee and window rules, QR and label-free flows, reason codes per SKU, and refunds that trigger automatically in the ERP or shop. Checkout shows delivery options, estimated delivery and pickup points. The captured pages give different figures for connected carriers — 1,000+ on several pages, 240+ on the transport page — so I asked and neither page resolves it. 3 4 5 7
The IT & Integration Lead
This is the heart of the product and it is documented deeply: more than a thousand carrier connections across roughly 190 countries plus 70+ pickup-point networks, shipping rules comparing real-time rates against the customer's own rate card or carrier API, customs documents with HS codes and electronic submissions, branded tracking with consolidated events, and a self-service returns portal where the warehouse scan triggers automated refunds and VAT-synced exchanges back into the ERP or shop. Checkout shows delivery options, estimated delivery and pickup points natively in the storefront. Analytics cover delivery times, cost per shipment and service-level adherence by carrier and route. 1 2 3 4 7
The Skeptic
This is the core and it is documented end to end: real-time rate evaluation with rule-based carrier selection (cost, service level, destination, carbon footprint), customs paperwork with HS codes and electronic submissions, branded tracking, and a self-service returns portal with per-item reason and condition codes, rule-based fees and windows, and refunds that trigger automatically into the ERP or shop. Own contracted rates are the working premise — the platform imports your rate card or pulls contracted rates from the carrier's API. The captured pages give different figures for connected carriers ("over 1,000" in places, "240+ already connected" on the transport page), so check your own carriers before buying the headline. 3 4 5 7
Freight & transport management
Show reasoningHide reasoning
How this is scored
Moving goods beyond parcels: pallet, groupage, full and part truckload, sea and air freight booked with carriers or forwarders, quotes and tenders compared, transport orders and documents (CMR, eCMR, delivery notes), shipment tracking across modes, freight cost audit, and CO2 emissions reported per shipment.
0 — No freight features; pallets and trucks are booked by phone and e-mail.
3 — A form to send a booking request to one forwarder, or freight rates shown without booking, tracking or documents.
5 — Pallet and groupage shipments booked with several carriers from one place, prices compared, transport documents generated, and the shipment status tracked.
8 — Spot quotes and tenders sent to many carriers with responses compared, the customer's own freight agreements and rate tables stored, eCMR or digital delivery notes, multi-modal tracking, freight invoices checked against the agreed price, and CO2 per shipment reported to a named standard (GLEC, ISO 14083).
10 — Transport management run in the system: route and load planning, dock and yard slot booking, carrier scorecards, freight cost allocated to orders and cost centres, and a carrier network that connects by API or EDI rather than by e-mail.
The E-Commerce Operations Lead
The transport management pages document road, sea and air with consolidation, multi-stop and temperature-controlled loads, pallet-level goods detail, and inbound flows where suppliers book under my carrier contracts in their own view. My tariffs come in via Libello or the carrier API, spot prices are shown per consignment, carrier invoices are audited against contracted rates with overcharge claims, and emissions per shipment follow a named NTM-based method feeding sustainability reporting. I found no public information on tenders or spot-quote comparison across many forwarders, and the captured pages do not name CMR or eCMR documents. 1 3 5
The Warehouse Manager
The transport management pages are concrete: road, sea and air transport, consolidation, inbound transport management, goods detail down to the pallet, temperature-controlled and multi-stop loads, own tariffs via Libello or carrier API, spot prices, and internal transfers booked as shipments with automatic cost-centre allocation even without a sales order behind them. Carrier invoices are checked against contracted rates with overcharges claimed back, and emissions per shipment run on a named European method (NTM) broken down by carrier, route and business unit. I found no public information on tenders compared across many carriers or eCMR-style digital delivery notes, which is the step above. 5 1 3
The Transport Planner
This is the part I care about most, and it holds up: road, sea and air with goods-level detail down to the pallet, my own tariffs stored via Libello or carrier API, spot prices, an invoice audit that checks every carrier invoice against contracted rates, and CO2 per shipment on an NTM basis for European shipments feeding sustainability reporting directly. What holds it back is that I found no public information on sending tenders to several forwarders with responses compared side by side, and no mention of eCMR or digital delivery notes — only generic label and freight document printing. 5 3 1
The Fulfilment Provider
The transport module covers road, sea and air with consolidation, multi-stop and temperature-controlled loads, inbound transport where my suppliers book under my carrier contracts, spot prices, freight cost calculated from my own tariffs, and an invoice audit that checks carrier invoices against contracted rates and claims overcharges — with cost-centre allocation even without a sales order. Emissions per shipment are reported on NTM-based factors for European shipments and feed sustainability reporting. We found no public information on tenders and quote comparison across many carriers, eCMR or digital delivery notes, or dock and yard booking. 5 3 1
The IT & Integration Lead
The transport-management pages document booking across road, sea and air with the customer's own tariffs via Libello or carrier API, spot prices per consignment, goods detail down to the pallet, inbound transport where suppliers book under the buyer's contracts, and multi-modal tracking across parcel, freight and ocean. Freight invoices are checked against contracted rates through the Cost module, emissions per shipment are calculated on an NTM basis, and costs are allocated to cost centres. We found no public information on tenders, eCMR or digital delivery notes, or dock and yard management. 1 3 5
The Skeptic
There is a genuine freight module: road, sea and air with consolidation and pallet-level detail, inbound transport where suppliers book under your own carrier contracts, internal transfers with automatic cost-centre allocation, spot prices, and an audit that checks every carrier invoice against contracted rates and claims back overcharges. CO2 per shipment is calculated to a named method — NTM-based for European shipments — and tracking events are normalised across parcel, freight and ocean. We found no public information on tenders sent to many carriers with responses compared, on eCMR or digital delivery notes by name, or on dock and yard slot booking. 1 3 5
Integrations, automation & exit
Show reasoningHide reasoning
How this is scored
How the tool fits the business around it: maintained connectors to shop systems, marketplaces, ERP and accounting (DATEV and the like), a documented API and webhooks, EDI for retail and logistics partners, rules that automate order routing and status updates, and a documented export of orders, stock and shipment history when the customer leaves.
0 — No integrations; orders are typed in or uploaded by hand.
3 — A CSV import and export and one or two shop connectors, with no API and no automation.
5 — Connectors to the main shop systems and marketplaces, a public API with documentation, and rules for common automations (order status, carrier choice, notifications).
8 — A broad connector list with ERP and accounting exports, webhooks, EDI (EDIFACT or similar) supported or offered through a named partner, rule engines for order routing across warehouses, and the API rate limits and versioning documented.
10 — The tool is an open part of the stack: every object readable and writable by API, a developer sandbox, connectors maintained by the vendor with a stated support policy, and a complete data export (orders, stock movements, shipments, documents) in open formats documented for the end of the contract.
The E-Commerce Operations Lead
450+ partner-certified, actively maintained connectors span the shop systems I run (Shopify, Magento, WooCommerce and PrestaShop are named), ERP (SAP, Microsoft Dynamics, NetSuite, Visma), WMS and payment providers, with a documented REST API, an on-premises XML route, EDI to carriers, and automation where order or pack confirmation triggers booking, labels and tracking. Data and price push run over standard consignment XML by FTP, SFTP or HTTP POST. Before signing I would still want webhooks, API rate limits and versioning, accounting exports like DATEV, and a documented end-of-contract export of my order and shipment history — we found no public information on any of those. 2 3 5 6 7
The Warehouse Manager
Four hundred and fifty-plus actively maintained integrations across shops, ERP, WMS and payment systems with real names — Dynamics, SAP, NetSuite, Visma, Blue Yonder, Ongoing, Shopify, Magento and more — plus a documented REST API for cloud, an XML option on-premise, EDI connections to carriers, and automation that books, prints and tracks from order or pack confirmation. Switching platforms without rebuilding the connections is stated outright. I found no public information on API rate limits and versioning, webhooks, or a documented full export of order and shipment history at the end of the contract, which is what separates the best from the very good here. 2 3 6 7
The Transport Planner
450+ actively maintained, certified integrations across e-commerce, ERP and WMS with named partners (SAP, Microsoft Dynamics, NetSuite, Visma, Blue Yonder), a documented REST cloud API plus an on-prem XML option, EDI connectivity to national and international carriers, and automation where order confirmation or pack confirmation triggers booking and labels. I found no public information on webhooks, API rate limits and versioning, or a documented export of orders and shipment history at the end of the contract. 6 2 3 7
The Fulfilment Provider
450+ maintained integrations validated through a certified partner program, with named shops (Shopify, Magento, WooCommerce, PrestaShop, Litium, Centra and more), ERP (Dynamics, SAP, NetSuite, Visma), WMS brands and payment providers, plus a documented REST API, an on-prem XML option and EDI connectivity to carriers — enough that the next client's platform is probably covered. Automation is event-driven: order confirmation or pack confirmation triggers booking, label and tracking. We found no public information on webhooks, API rate limits and versioning, a developer sandbox, accounting exports like DATEV, or a documented export of orders and history at the end of the contract. 2 6 7 3
The IT & Integration Lead
From my desk this is strong: documented REST (APIConnect) and on-premises XML (OnlineConnect) APIs, EDI connectivity to carriers, and 450+ connectors spanning shops, ERP and WMS — Dynamics, SAP, NetSuite, Visma, Blue Yonder and more — with a stated commitment that every integration is actively maintained and validated through a certified partner program. Automation is concrete: order confirmation triggers booking and label creation, pack confirmation triggers the carrier booking, and carrier status flows back into the WMS. We found no public information on webhooks by name, API rate limits and versioning, a developer sandbox, or a documented export of data at the end of the contract. 2 3 5 6 7
The Skeptic
The 450+ integrations are backed by names, not just logos — Microsoft Dynamics, SAP, NetSuite and Visma on the ERP side, six-plus WMS platforms, seven-plus shop systems — plus a documented REST API, an on-prem XML alternative, EDI connectivity, and automation where pack confirmation triggers booking and carrier status flows back into the WMS. A certified partner programme validates and actively maintains the connectors, which is more commitment than most logo walls show. My exit question is unanswered: we found no public information on webhooks, on API rate limits and versioning, or on a documented export of order and shipment history when the contract ends. 2 3 6 7
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where order, customer and shipment data are hosted, and who the subprocessors are (hosting, carriers' label APIs, payment, e-mail, analytics). Independently sourced by the sovereignty pipeline; recipient addresses flow to every connected carrier, so the processing chain counts, not only the server.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no privacy policy that covers the service.
3 — A privacy policy exists, but hosting location is unstated or non-EU and the processors behind the service are not named.
5 — EU hosting stated and an EU contracting entity, but parts of the chain (support, e-mail, analytics, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with locations, a data processing agreement offered for the recipient and customer data, and the role of carriers (as independent controllers or processors) explained.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, data export and deletion documented, and a security certification (ISO 27001, SOC 2 or BSI C5) published rather than implied.
The E-Commerce Operations Lead not rated — no public information
We found no public information on the contracting entity's location, where order, customer and shipment data are hosted, or which subprocessors sit behind the service; no hosting statement, data processing agreement or security certification appears on the pages we captured. Since recipient addresses flow to every connected carrier, I would need this chain documented before putting my customer data through it. 1 5 6
The Warehouse Manager not rated — no public information
I found no public information in the captured pages on the contracting entity and its parent, where order and customer data are hosted, the subprocessors behind the service, or any data-processing agreement or security certification, and no sovereignty attributes were on record for this vendor. I leave this unscored rather than read anything into the vendor's name. 1 4 5
The Transport Planner not rated — no public information
I found no public information on where order, customer and shipment data are hosted, the contracting entity's location, subprocessors, a data processing agreement or any security certification in the captured pages; no sovereignty attributes are on record. 1 6
The Fulfilment Provider not rated — no public information
We found no public information on the contracting entity, hosting location for order and recipient data, subprocessors such as hosting or carrier label APIs, a data processing agreement, or any security certification on any page we read. Recipient addresses flow to every connected carrier, so this silence matters to me, but nothing on the captured pages lets me score it. 1 2 3 4 5 6 7
The IT & Integration Lead not rated — no public information
We found no public information on hosting location, the contracting entity's details, subprocessors, a data processing agreement or security certification; the captured homepage, integration and product pages carry none of it. The nearest fact is an on-premises XML connectivity option, which is a deployment choice rather than a statement about where order and recipient data are hosted. Recipient addresses flow to every connected carrier, and the processing chain behind that is undocumented on these pages. 1 5 6
The Skeptic not rated — no public information
We found no public information on hosting location, subprocessors, data processing agreements or security certifications on the captured pages; the only datum is the Swedish-form vendor name, nShift Group AB. Recipient addresses flow to every carrier booked through the platform, so demand the subprocessor list and hosting region in writing before signing. 1 5
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: subscription per tier, user, warehouse or module, the per-order, per-label or per-shipment fees, label rates and surcharges when shipping through the vendor's contracts, connector and setup fees, hardware, minimum term, and what happens to the data on cancellation.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or "from" figure exists, but the volume fees, included orders or labels, and how the price scales are unclear.
5 — Prices per tier are public with the main inclusions, but at least one commonly needed piece (per-order or per-label fees beyond the allowance, connectors, extra users or warehouses, onboarding) is unpriced or "on request".
8 — Every tier priced publicly with included volumes and the fee per order, label or shipment beyond them, add-ons and setup listed, minimum term and VAT treatment stated, and whether own carrier contracts are allowed on each tier said plainly.
10 — Complete price computability: annual cost derivable for a given order volume, warehouse count and module set, with every fee, label surcharge, hardware and support cost and the cancellation and data-return terms published.
The E-Commerce Operations Lead
The Returns pages publish a three-tier structure — Essential, Professional, Premium — showing which features sit in each (the branded returns widget in all three; BI API, customs declaration, warehouse function and exchanges in Premium), but we found no price figures on any captured page: no subscription numbers, per-order or per-label fees, included volumes, term lengths or setup costs. With tier names and no numbers I cannot budget a year of 300-parcel days without a sales call. 1 4 5
The Warehouse Manager
The returns pricing page names three tiers — Essential, Professional and Premium — and is clear about which features sit where: branded returns widget in all three, warehouse function, exchanges, customs declaration and the analytics API only in Premium. I found no figures in the captured pages for the subscription, per-shipment or per-label fees, setup, or minimum term; a buyer evaluation pack is offered in place of numbers, so no annual cost can be worked out from public pages. 4 5
The Transport Planner
Three tiers named Essential, Professional and Premium are published with their feature inclusions — the branded returns widget in every tier, customs declaration, warehouse function, exchanges and the BI API only in Premium — but no price figure appears anywhere. I found no public information on subscription prices, per-shipment fees, setup costs, minimum terms or what happens to the data on cancellation. 4
The Fulfilment Provider
The returns pages publish a three-tier structure — Essential, Professional, Premium — with which features sit in which tier, but we found no public price figures anywhere: no subscription cost, per-order or per-label fees, connector or setup fees, minimum term, or VAT treatment. As a buyer I cannot compute an annual cost from these pages alone; it is a sales conversation. 4
The IT & Integration Lead
The only pricing facts captured are the Returns tier structure — Essential, Professional and Premium — with feature inclusions such as customs declaration, BI API and warehouse function allocated per tier. Beyond that we found no public information on figures: subscription, per-order or per-label fees, setup and connector costs, minimum term, or cancellation and data-return terms. 4
The Skeptic
The returns product publishes three tiers — Essential, Professional and Premium — with feature placements (customs declaration, exchanges and the warehouse function only in Premium), so some structure is visible. The figures are not: we found no public information on subscription prices, per-order or per-label fees, connector and setup costs, minimum term or data-return terms on cancellation. A "buyer evaluation pack" for procurement is offered, which tells you how the number reaches you: through sales. 4 5
Questions about nShift
Is nShift European?
Not determined: the vendor’s pages as captured do not say where nShift is based.
Where does nShift store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does nShift have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to nShift?
As of 4 Nov 2026, the panel rates Ongoing WMS (3.5/5), Shippingbo (3.5/5) and Mintsoft (3/5) highest among the other 19 Supply Chain & Logistics products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Ongoing WMS (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: nShift alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (nshift.com, nshift.com/integration-partners/wms, nshift.com/delivery-management/multi-carrier-shipping-software, nshift.com/products/returns, nshift.com/products/transport-management-system, nshift.com/integration-partners and 1 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 32 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.nshift.com Checked 3 Nov 2026 Details →
- 2 Warehouse operations: receiving, picking & packing — found from sitemap nshift.com Checked 3 Nov 2026 Details →
- 3 Multi-carrier shipping & returns — found from sitemap nshift.com Checked 3 Nov 2026 Details →
- 4 Multi-carrier shipping & returns — found from sitemap nshift.com Checked 3 Nov 2026 Details →
- 5 Freight & transport management — found from sitemap nshift.com Checked 3 Nov 2026 Details →
- 6 Integrations, automation & exit — found from sitemap nshift.com Checked 3 Nov 2026 Details →
- 7 Integrations, automation & exit — found from sitemap nshift.com Checked 3 Nov 2026 Details →