New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Best WMS: native, bolt-on, or stand-alone

The best WMS for a 30 to 100 person distributor is the warehouse layer that matches sites, bins, orders, and scan steps.

FlecticUpdated 25 min read

The best WMS for a 30 to 100 person distributor is the warehouse layer that matches sites, bins, orders, and scan steps. As of October 2026, Business Central Essentials is USD 80 per user per month paid yearly, and that license sits on warehouse features that run from order posting through directed put-away and pick. Wave processing, cluster picking, and a warehouse app beside the ledger show up on Supply Chain Management at USD 210 per user per month, same yearly basis. This page maps native ERP warehouse, a bolt-on WMS, and stand-alone plans. Our guide to what a warehouse management system is holds the category definition.

What an ERP and a WMS each do

An ERP keeps the commercial record: sales orders, purchasing, inventory value, and the general ledger. A WMS directs the floor: where a unit sits, who moves it, and in what sequence. Microsoft builds both ideas into Dynamics 365, at two depths. Business Central adds warehouse activities on top of inventory so complexity can grow with the company, from posting on orders up to directed put-away and pick, as described in Manage warehouse activities. Supply Chain Management warehouse management is built around waves, work, and location directives, and it ties those tasks to transportation, manufacturing, quality, purchasing, transfers, sales, and returns (warehouse management overview).

Buyers who are still on spreadsheets describe the gap in operational language. One team wrote that "managing inventory manually is becoming a nightmare. We're currently using spreadsheets" and asked for "inventory tracking, bin locations, and order fulfillment without being overly complicated or ridiculously expensive" (buyer post, February 2025). Another operation said "Nothing talks to each other, inventory visibility is rough, and ordering is a mess" (warehouse recommendations thread). Those sentences are the decision: one system of commercial record, plus enough direction on the floor that people stop retyping quantities.

For a single company that sells, buys, and stocks in the same legal entity, the ERP should own orders and valuation first. Warehouse execution is a layer you turn up inside that ERP, bolt on beside it, or buy as its own product. Business Central warehouse management walks the Microsoft tiers in more detail. The rest of this page is how to choose the layer.

What Business Central includes before you buy a WMS

Business Central does not jump from a quantity on hand to a full execution engine. Microsoft documents a progression you combine as the building gets harder (design details):

  1. Post receipts and shipments on the order itself.
  2. Use basic warehouse receipt and shipment, or inventory put-away and pick.
  3. Use advanced warehouse receipt, put-away, shipment, and pick.
  4. Turn on directed put-away and pick.

A Shelf No. on the item or stockkeeping unit is informational. It copies onto document lines and reports. It is not used in warehouse activities or availability. If the only aisle reference is that Shelf No. field, the system is still posting a quantity, and the picker is still hunting.

Bin code is optional until directed put-away and pick is on. Then bin code is mandatory. Advanced warehouse setup is where bin capacity, weight, bin ranking, zones, warehouse classes, and bin types (RECEIVE, SHIP, PUT AWAY, PICK, PUTPICK, QC) live. Put-away templates and FEFO picking are documented for directed or bin-policy setups. Microsoft's setup list also includes bin contents, default bins, locations that use bins, cycle counting, and automatic break-bulk (Configure warehouse processes).

Two rules change how you staff and how you store:

  • Each person who performs warehouse activities must be a warehouse employee. Work is filtered to that employee's default location. They can open other assigned locations and still cannot perform activities there (Set Up Warehouse Employees).
  • Bin contents keep multiple units of measure only at locations that use directed put-away and pick. Every other configuration stores the bin in the item's base unit of measure.

Directed put-away and pick is the top of this ladder. It is the right test before any bolt-on conversation: bins are real, put-away follows a template, picks can follow FEFO, and cycle counts run inside the same product that posts the order. Microsoft's Business Central warehouse design page does not document license plates, wave picking, or labor management. If your operation needs those, you are past this module. That is a scope fact, and it belongs in the selection notes.

License math stays on the ERP price list. As of October 2026, US list prices paid yearly are Essentials USD 80, Premium USD 110, and Team Members USD 8 per user per month (Business Central pricing). Canadian list prices on the same basis are Essentials CAD 108.50, Premium CAD 149.20, and Team Members CAD 10.90, plus applicable tax (Business Central pricing, Canada). Assume 10 people who need Essentials because they post orders and warehouse documents: 10 times USD 80 is USD 800 per month before tax, paid yearly. Confirm with your licensing specialist which of those people can register as warehouse employees. Team Members at USD 8 are a different license. Do not assume a pick license is the cheap seat.

What Odoo Inventory includes before a separate WMS

Odoo 19 defines a warehouse as a physical space with an address. A new database starts with one warehouse, short name WH, and that short name allows at most five characters. Multi-step routes have to be enabled before a warehouse can run one-step, two-step, or three-step incoming or outgoing shipments (Warehouses, Odoo 19). With the route off, the receipt is still a single posting.

On its Inventory features page, Odoo lists locations that can stand for shelves, aisles, cold rooms, and pallet racks. Putaway rules can use storage categories. Removal strategies listed are FIFO, FEFO, nearest zone, and LIFO. Picking methods listed are single, batch, cluster, and wave. Barcode scanning is described for receipts, pickings, and inventory adjustments, with GS1, EAN-13, and EAN-14. Costing methods listed are FIFO, average cost, and standard price. Landed costs can include vendor bills, taxes, tariffs, fuel surcharges, and handling fees. Carrier labels named on that page are FedEx, DHL, UPS, USPS, Bpost, Sendcloud, EasyPost, and Shiprocket (Odoo Inventory features). Treat the features page as the vendor's own list. Have a partner show wave or cluster picking and a GS1 scan on your items before you depend on them. That page is not a claim that Odoo replaces a high-volume automation engine.

Subscription shape, as of October 2026 (Odoo Pricing):

  • One App Free (Published USD figure: USD 0 · What the page says you get: One app, unlimited users, Odoo Online)
  • Standard (Published USD figure: USD 31.10 and USD 38.90 per user per month · What the page says you get: All apps, including Inventory. Discount lasts 12 months for the initial users ordered)
  • Custom (Published USD figure: USD 61.00 and USD 76.20 per user per month · What the page says you get: Same app inclusion and the same 12-month initial-user discount. Odoo.sh hosting is extra)
  • Light User (Published USD figure: USD 8.90 · What the page says you get: Inventory Barcode Operator among the Light User capabilities. Sold through an advisor quote)

Standard and Custom include support, hosting, and maintenance as Odoo describes those plans. Implementation services are excluded, and so is Odoo.sh. The page shows two amounts for Standard and two for Custom. Use both figures in a budget and ask the advisor which one applies after month 12. Assume 8 standard users at the higher displayed Standard amount of USD 38.90 and 6 Light Users at USD 8.90 for barcode work: about USD 311 plus USD 53 per month, USD 364, before implementation. Light User is a barcode operator seat on that price card. It is not a second WMS.

When a bolt-on WMS is justified

Stay on the native module while the building still matches what that module directs.

Business Central is usually enough when you have one primary site, picks follow a bin and a put-away template, FEFO or break-bulk covers the product rule, and the same employees always work their default location. Odoo Inventory is in the same band when one-, two-, or three-step routes describe the dock, storage categories can place product, and the listed removal strategy (FIFO, FEFO, nearest zone, or LIFO) matches how you already rotate stock. Configure those controls and run cycle counts before you fund a second product. A dirty item master will mis-direct a WMS the same way it mis-directs a bin.

A bolt-on WMS is justified when the native screen cannot direct the move. Count these pressures. Microsoft and Odoo do not publish an orders-per-day failure line, so the count is yours:

  1. You need outbound waves, cluster picking, containerization, or a scanner app that creates warehouse work from location directives. Those are Supply Chain Management warehouse processes, including stocking limits, batch and serial control, pallet and container types, Zebra ZPL labels, simple cross-docking, and the Warehouse Management mobile app (overview).
  2. You have more than one site and Business Central warehouse employees cannot perform activities outside their default location, so each building is its own execution setup.
  3. Product moves in several units of measure in the same bin, and you are not willing to turn on directed put-away and pick to make that legal in Business Central.
  4. You want warehouse execution, carrier connections, or automation while the general ledger and the sales order stay in the ERP you already run.
  5. Pickers still work from paper or from a spreadsheet export, and scan misses show up as reships.

A perishable catalog makes FEFO and lot behavior the test, not a brand name. One warehouse lead described "The warehouse alone has 50,000+ unique SKUs, mostly perishable food items" (same recommendations thread). That post is one company's load. It shows why removal strategy and expiry have to be demonstrated on your items. It is not a threshold where every distributor must leave the ERP.

The Microsoft bolt-on: warehouse management only mode

Microsoft's own bolt-on pattern is warehouse management only mode. A Supply Chain Management legal entity runs warehouse processes for an external ERP or order system. Inbound and outbound shipment orders replace sales, purchase, and transfer orders. Microsoft names automation integration, carrier integration, and the Warehouse Management mobile app as reasons to deploy it beside an existing ERP (Warehouse management only mode).

That is the clean answer when you want warehouse management beside Business Central while financials stay put. Financials and the original sales order can stay in the external ERP. The warehouse legal entity works shipment orders. You still have two products, two administration surfaces, and an integration that has to create those shipment orders. A buyer who had already added a WMS put the extra stack plainly: "you end up bolting on a separate integration layer and a shipping tool alongside the WMS" (SnapFulfil thread). Another described the ongoing cost of a second system that holds inventory the ERP does not post: "eliminating the manual reconciliation between NetSuite and whatever bolt-on system holds the data NetSuite can't natively touch, inventory in a WMS" (NetSuite thread). Budget that layer as its own line. Ask each bidder to show the shipment-order message for one real order, one receipt, and one return.

Out of the box, warehouse management only mode does not support production, batch, or kanban processing on shipment orders. It does not support catch-weight items on those orders. It does not run the transportation-management charge and freight-bill engines on shipment orders. It does not let you create outbound shipment orders from the mobile app. If you manufacture, sell by catch weight, or rate freight inside the same shipment document, have those three gaps demonstrated. A partner app on Business Central is a second bolt-on pattern. Make the vendor show the app on your items, your bins, and your scanner. Do not accept a feature grid in place of that session.

Supply Chain Management list price, as of October 2026, is USD 210 per user per month for Supply Chain Management and USD 300 for Premium, paid yearly (Supply Chain Management pricing). The pricing page does not list a device or scanner license, so keep hardware and any activity license as a quote line. Assume 6 warehouse users on the USD 210 license: USD 1,260 per month paid yearly, plus the Business Central users who still post the commercial order. Our Business Central implementation work scopes that split so finance stays on Business Central and the warehouse phase has its own acceptance tests.

How to choose among native, bolt-on, and stand-alone

Use one row at a time. The cell is what you should see in a working session, on your data.

  • Who owns the general ledger (Native ERP warehouse: Business Central or Odoo posts orders, value, and the ledger · Bolt-on WMS on the same ERP: External ERP keeps the ledger. SCM warehouse-only mode posts shipment orders · Stand-alone WMS or inventory suite: Ask which product posts revenue and inventory value. Many suites are stock systems first)
  • Sites (Native ERP warehouse: BC: activities only at the employee default location. Odoo: Starts with one warehouse (short name WH, five characters). Enable multi-step routes before one-, two-, or three-step incoming or outgoing shipments. · Bolt-on WMS on the same ERP: A warehouse legal entity can run buildings for an outside order system · Stand-alone WMS or inventory suite: Compare the plan's location cap to your buildings, not to a demo company)
  • Bins and put-away (Native ERP warehouse: BC: bins mandatory only under directed put-away and pick, with templates, zones, and bin types. Odoo: locations and storage-category putaway on the features list · Bolt-on WMS on the same ERP: Location directives, stocking limits, and volumetrics in SCM · Stand-alone WMS or inventory suite: Zoho publishes bin caps by plan. Others sell "advanced warehouse" as a higher plan or a quote)
  • Pick method (Native ERP warehouse: BC: directed pick, FEFO, break-bulk. Waves and cluster picks are not on the BC design page. Odoo lists single, batch, cluster, and wave · Bolt-on WMS on the same ERP: SCM: multiple strategies, outbound waves, cluster picking, containerization · Stand-alone WMS or inventory suite: Cin7 describes advanced warehouse management as multi-location mobile picking with FIFO and FEFO enforcement)
  • Scan confirmation (Native ERP warehouse: Odoo lists barcode on receipts, picks, and adjustments, and a Light User barcode operator. Have BC scanning shown on your devices · Bolt-on WMS on the same ERP: SCM Warehouse Management mobile app, named for scanners · Stand-alone WMS or inventory suite: Require a pick scan on your busiest order, including a short pick)
  • Lots, serials, FEFO (Native ERP warehouse: BC: FEFO on directed or bin-policy setups. Odoo lists FEFO as a removal strategy. · Bolt-on WMS on the same ERP: SCM lists batch and serial control. Catch weight on shipment orders is unsupported in warehouse-only mode · Stand-alone WMS or inventory suite: Fishbowl includes lot and traceability on the Scale plan, not on Essentials)
  • License plates, labor, automation (Native ERP warehouse: Do not expect these from the Business Central warehouse design page · Bolt-on WMS on the same ERP: SCM documents the execution depth, and warehouse-only mode cites automation integration as a deployment reason · Stand-alone WMS or inventory suite: Enterprise brands aimed at large retail networks do not publish a small-distributor list price)
  • Integration you must fund (Native ERP warehouse: One product, if the tier is high enough · Bolt-on WMS on the same ERP: Shipment orders in, status and inventory back. Carrier or shipping tools may be extra · Stand-alone WMS or inventory suite: Same risk: a second system plus a shipping tool)

A practical reading of that table: a single legal entity, one main building, and no wave, cluster, or automation requirement should finish directed put-away in Business Central, or multi-step routes and barcode operators in Odoo, before a second platform is priced. A distributor that already runs waves, cluster picks, or building automation, or that must keep a different ledger, should price warehouse management only mode or a stand-alone plan as an execution project with its own interface tests.

Someone in a mixed retail and food business asked "is one ERP realistic, or are we better off with a best-of-breed approach" with a dedicated WMS feeding a lighter ERP (recommendations thread). One ERP is realistic when the native warehouse tier passes the table on your sites and your pick method. A dedicated WMS feeding a lighter ERP is realistic when the ledger is simple and the floor is not. The expensive version is both a heavy ERP warehouse module you never configure and a WMS you never integrate.

What small-warehouse plans cost per month

Published prices below are vendor list figures as of October 2026. Read them as categories, so you can see what each meter is, and keep the buying decision on the criteria table above. Enterprise names that show up in retail roundups, including Manhattan, Blue Yonder, and SAP EWM, do not publish a small-distributor list price in the pages this comparison uses. Leave them for a quote if you run a multi-node retail network. For a 30 to 100 person wholesale building, start with the meters.

Inventory trackers price unique items and users. Sortly is stock-tracking software, not directed warehouse execution. As of October 2026 its Ultra plan, marked most popular, includes 2,000 unique items and 5 user licenses. Premium includes 5,000 unique items, 8 users, and QuickBooks Online. Advanced is a first-year yearly equivalent of USD 24 per month (USD 288 billed for the year, described as half off the first year for new customers) or USD 49 month to month, for 500 items and 2 users. Ultra is USD 74 first-year yearly equivalent (USD 888 for the year) or USD 149 monthly. Premium is USD 149 first-year yearly equivalent (USD 1,788 for the year) or USD 299 monthly. Advanced's note says that after year one a 20% yearly discount applies (Sortly pricing). If you need bins, waves, or scan-directed picks, this category is the wrong tool.

Zoho below Premium is an order, user, and location cap and has no published bin cap. Standard is USD 29 per organization per month, billed annually: 500 orders a month, 3 users, 2 locations. From Premium up, bins are capped too. Premium is USD 79 (3,000 orders, 5 users, 4 locations, 500 bins per location), Plus is USD 129 (7,500 orders, 10 users, 6 locations, 500 bins per location), and Enterprise is USD 249 (15,000 orders, 10 users, 10 locations, 5,000 bins per location). An advanced warehousing add-on is USD 124.17 per organization per month, billed annually (Zoho Inventory pricing). A buyer leaving spreadsheets said "Zoho feels too new, and Cin7 is pricey for our needs" (February 2025 post). Put the caps next to that reaction. Premium's 500 bins per location is a hard planning number. Enterprise's 5,000 bins is the jump. If you are already near 500 bins in one building, the add-on and the Enterprise cap belong in the same quote.

Fishbowl prices inventory by plan and then an advanced warehouse starting price. Essentials is USD 229 per month billed annually and includes 2 users. It does not include manufacturing bills of material, work orders, or MRP. Growth is USD 429 per month billed annually, 5 users. Scale is USD 729 per month billed annually, 10 users, and lot and traceability start on Scale. Advanced Warehouse starts at USD 595 per month, priced by users and deployment, quote required. An implementation package is required with purchase, and Fishbowl describes a 6 to 8 week training certification (Fishbowl pricing).

Cin7 meters users and annual sales orders. The page does not publish a location cap. Per month, taxes excluded, with no commitment term stated: Standard is USD 349 for 5 users and 6,000 sales orders a year. Pro is USD 599 for 10 users and 24,000 sales orders a year. Advanced is USD 1,199 for 15 users and 120,000 sales orders a year, with more orders available to purchase. Advanced warehouse management, described as multi-location mobile picking with FIFO and FEFO enforcement, is included on Advanced and is an add-on on Pro (Cin7 pricing). Pro adds that advanced-warehouse add-on and still has no location cap on this price card.

Work the Cin7 meter on purpose. Assume 40 orders a day and about 250 shipping days: 10,000 sales orders a year. That is above Standard's 6,000 and inside Pro's 24,000, so the subscription conversation is Pro at USD 599 per month plus the advanced warehouse add-on if you need that mobile FIFO/FEFO picking. Assume 200 orders a day and 250 shipping days: 50,000 sales orders a year, still inside Advanced's 120,000, at USD 1,199 per month before extra orders and tax. A 400-order day over 250 days is 100,000 sales orders, close to the Advanced cap. Extra orders are a purchase. Model them before peak season.

ERP licenses that already include a warehouse tier sit beside those subscriptions, not under them. Business Central Essentials at USD 80 or Premium at USD 110 per user per month, Odoo Standard or Custom at the paired amounts above, and Supply Chain Management at USD 210, are user licenses. They do not meter annual sales orders the way Cin7 does, and they do not meter bins the way Zoho Premium does. The constraint is functional: which tier you turn on, and which processes warehouse-only mode will not run.

A selection sequence you can run with two bidders

Run the same script with whoever configures Business Central, whoever configures Odoo, and any stand-alone bidder. Named people, hours, a phase plan, and code ownership decide the award. A partner badge does not.

  1. Export last quarter: order count on the busiest day, order count for the year, location count, active SKUs, bin count if you have one, and the share of lines that are lot, serial, or expiry controlled.
  2. Write the pick method you use today in one sentence: single order, batch, cluster, or wave. If you do not wave today, do not buy a wave engine because a demo looked fast.
  3. Ask for a directed session on your file: receive a purchase order, put it to a bin with a capacity or a storage category, pick with FEFO if you expire product, short-pick one line, and cycle-count a bin the picker was not told the quantity for. One buyer flagged the last point directly, asking "whether blind-count mode is a first-class feature or bolted on" (license-plate count thread). Watch the scanner. Clunky counts become skipped counts.
  4. For a bolt-on, require the message list: shipment order create, pick confirm, inventory adjustment, and return. Time a failure, such as a shipment order that arrives with an unknown item.
  5. For carriers, start from the names Odoo prints (FedEx, DHL, UPS, USPS, and the others on the Inventory features page) or from the carrier integration Microsoft cites for warehouse-only mode. If your carrier is absent, it is a third system. Price it.
  6. Split the quote into license, implementation, data load, devices, and integration. Odoo says implementation is outside the subscription. Fishbowl requires an implementation package. Business Central and Supply Chain Management project fees belong on the bidder's paper. Ask for each line in writing.
  7. Name who owns the code and the configuration after go-live, and who is on the floor during the first cycle count. Keep the first phase to native warehouse configuration on clean items, bins, and one pick method. A bolt-on with shipment orders and a carrier is a later phase, with its own acceptance tests.

ERP implementation is how we stage that first phase. Supply chain implementation is the broader flow when purchasing and transfers have to move with the warehouse. Companies with several nodes and a carrier stack usually start from logistics and supply chain implementation so the warehouse phase is planned with the rest of the operation.

Mistakes that make the warehouse project miss

Buying a WMS while Shelf No. is still pretending to be a bin. Fix the location model inside Business Central or enable real warehouses and routes in Odoo, then decide.

Treating a bin cap or an order cap as fine print. Zoho Premium stops at 500 bins per location. Cin7 Standard stops at 6,000 sales orders a year. Those are contract numbers. Map them to last year's actuals and to next peak, not to an average Tuesday.

Staffing Business Central as if every login can pick in every building. Warehouse employees act at their default location. Multi-site work means a setup per location, or a different product.

Ignoring warehouse-only mode gaps. Production, catch weight, and transportation charges on shipment orders are documented exclusions. Discovering them after go-live means the ERP still does that work, badly, in a spreadsheet.

Letting a shipping tool appear in week six. If labels are not in the WMS session you watched, they are another bolt-on. Odoo names specific carriers. Anything else needs a demo on your account numbers.

Signing a stand-alone inventory suite because the monthly number is lower than an ERP user stack, then discovering it does not post the ledger you need. Sortly's own positioning is item tracking. Cin7, Zoho Inventory, and Fishbowl publish warehouse depth at higher plans. Ask who owns inventory value and margin. If the answer is a monthly export to the accountant, you have recreated the spreadsheet.

Comparing enterprise retail WMS brands to a 40-person distributor on list price. They do not publish that list price. Your comparison set is native ERP tiers, warehouse management only mode, and the published small-business plans above.

Where this leaves the buy

Pick native Business Central or Odoo warehouse when bins, FEFO, routes, and a scan you have watched will cover the next peak. Pick a bolt-on, with warehouse management only mode as the Microsoft pattern to test, when waves, cluster picks, automation, or a separate ledger are already true of your building. Pick a stand-alone plan when its published meter (users, orders per year, bins per location) covers your count and you have seen a short pick on your scanner. Bring the busy-day order count, the bin count, and the scan-miss history to the call. We will tell you which column of the table you are in, and what the first phase should leave out.

How Flectic can help

Flectic implements Dynamics 365 or Odoo for logistics and supply chain operators, connecting the warehouse, transport, billing and finance so the invoice matches the work done. Flectic sends a written proposal with a fixed price for each phase before work starts. For the full scope, see ERP for logistics and supply chain. Book a free discovery call with Flectic to decide whether your warehouse needs a bolt-on or the native module.

Sources

Frequently asked questions

Does Cin7 or Zoho Inventory count as a WMS or only as inventory software?

Treat the plan name as the answer. Zoho Inventory Premium and Plus include 500 bins per location, and Enterprise includes 5,000, with advanced warehousing sold as an add-on. Cin7 includes advanced warehouse management, multi-location mobile picking with FIFO and FEFO, on the Advanced plan and as an add-on on Pro. Zoho below Premium is an order, user, and location cap (Standard: 500 orders a month, 3 users, 2 locations) and has no published bin cap. Cin7 Standard is 5 users and 6,000 sales orders a year. Pro adds the advanced-warehouse add-on and still has no location cap on the published card. Sortly prices unique items and users and is stock tracking, so it sits outside this comparison.

Can Dynamics 365 warehouse management run beside Business Central without replacing financials?

Yes, if you use warehouse management only mode. A Supply Chain Management legal entity runs the warehouse for an external ERP using inbound and outbound shipment orders, and Microsoft cites automation, carrier integration, and the mobile app as reasons to deploy it that way. Sales orders and the ledger can stay where they are. Out of the box, that mode does not run production, batch, or kanban on shipment orders, catch-weight items on those orders, or transportation charge engines on shipment orders.

Which carriers are included, and which need another system?

Odoo names FedEx, DHL, UPS, USPS, Bpost, Sendcloud, EasyPost, and Shiprocket on its Inventory features page. Microsoft cites carrier integration as a reason to run warehouse management only mode beside an existing ERP, and it does not print a carrier list on that overview. Business Central's warehouse design page does not list carriers. Ask the bidder to print a label for your account during the working session. If the label comes from a second product, price that product on its own line.

Is one ERP realistic, or should a dedicated WMS feed a lighter ERP?

One ERP is realistic when directed put-away, bins, FEFO, and the routes your warehouse uses can be shown on your items inside Business Central or Odoo. A dedicated WMS feeding a lighter ERP is realistic when the floor needs waves, cluster picks, or automation and the ledger can stay simple. The costly pattern is an ERP warehouse module nobody configures plus a second system nobody integrates. Decide from sites, bins, and pick method, then fund the integration as its own quote line.

What is extra beyond the monthly WMS price for users, orders, and bins?

Read the meter on the plan. Cin7 Standard includes 5 users and 6,000 sales orders a year, Pro includes 10 users and 24,000, and Advanced includes 15 users and 120,000, with more orders available to purchase. Zoho caps bins at 500 per location on Premium and Plus and at 5,000 on Enterprise, and prices an advanced warehousing add-on separately. Fishbowl Advanced Warehouse starts at a quoted monthly price by users and deployment, and an implementation package is required. Odoo excludes implementation and Odoo.sh from the subscription.

How many orders or SKUs should push us off native bins?

Use your own busy day, because a universal cutoff is the wrong tool for this decision. Export last quarter's busiest day, the year's sales orders, active SKUs, locations, and bin count if you have bins. Compare orders and users with the Cin7 caps and bins with the Zoho caps if those products are in the quote. Inside Business Central, move up the documented tiers until directed put-away and pick is on, then look at a bolt-on only if you still need waves, cluster picks, or work outside the employee's default location.

How do we pick a WMS without crowning a single vendor?

Score three columns on your data: the native ERP warehouse, a bolt-on such as warehouse management only mode, and a stand-alone plan with a published user, order, or bin cap. Require the same working session from every bidder: a receipt, a directed put-away, a short pick, and a cycle count the picker was not pre-told. Split the quote into license, implementation, devices, data load, and integration. Named people, hours, the phase plan, and who owns the configuration after go-live decide the award.