Inventory planning software for D2C brands on Shopify that also sell on Bol and Amazon

Rewize plans how much stock each SKU needs, in which warehouse, 3PL or marketplace pool, for the coming lead time, across Shopify, Bol and Amazon. That is the job of inventory planning software: it looks ahead, while inventory management in the WMS or 3PL counts what is on the shelf today. Rewize is inventory forecasting and purchase planning software for eCommerce brands.

More than 100 D2C brands plan their stock with Rewize.

In short

  • Rewize plans stock per warehouse, 3PL, Bol FBB pool and Amazon FBA pool, counting each sale at the location that shipped it.
  • Every SKU gets days of cover and one of six health statuses, from Out of stock to Overstock.
  • Surplus never moves between locations by itself: the planner creates the transfer order.
  • Approved purchase orders go back to Picqer or Exact Online, and nothing leaves Rewize without a planner's approval.
  • Most brands are live within 1 to 7 days, with pricing based on annual revenue.

What inventory planning is, and how it differs from inventory management

Inventory planning sets the stock level per SKU and per location that covers forecast demand through the supplier's lead time. Inventory planning does this without tying up more cash than needed. Inventory management is the job of a WMS: it keeps track of what sits where today and handles picking.

Many tools sold as inventory management software are warehouse or ERP systems. The difference between a planning tool, WMS or ERP is the job each one does. Rewize sits on top of the WMS or ERP to do the planning.

Inventory optimisation is the word larger companies often use for much the same job.

Inventory management (WMS or 3PL)

  • What is on the shelf at each location today
  • Receiving, picking and shipping orders
  • Stock counts per location

Inventory planning (Rewize)

  • How much each SKU needs per location for the coming lead time
  • Days of cover and health status per SKU
  • Purchase orders sized to the coverage target, approved by a planner
Inventory management in a WMS or 3PL shown next to inventory planning in Rewize.

Brands often have enough stock in total, but in the wrong place. Rewize regularly sees multichannel brands with far too much stock at Amazon or in one 3PL. That stock then has to be moved.

Most multichannel brands Rewize works with have run into this at some point.

Brands also get stuck when the planning spreadsheet no longer keeps up. Past roughly 60 to 100 SKUs and several channels, the planning file gets complex. It often sits with one person who understands it.

Who this is for, and who it is not for

Rewize's inventory planning fits D2C brands that sell through several channels and hold stock in more than one place:

  • 50 to 1,000+ SKUs. The point when Excel stops working usually comes past roughly 60 to 100 SKUs.
  • Two or more channels. The brand's own Shopify store plus Bol, Amazon, retail or B2B.
  • A brand's own warehouse plus a 3PL or WMS. For example a 3PL such as Monta, or a warehouse run on Picqer.
  • Stock in Bol FBB or Amazon FBA. Rewize plans marketplace stock as its own location.
  • A planner who has to decide how much stock each location needs. That is usually the founder, the operations manager or the buyer who places the orders.

Rewize customers range from €500K to €80M in annual revenue.

Rewize is not the right fit for:

  • One channel, one location and fewer than 50 SKUs. At 15 to 20 products on a single channel, Excel is still the right tool.
  • Fresh produce. Rewize is built for products that can sit in a warehouse through a long lead time.
  • Resellers who reorder daily with lead times of 1 to 5 days. A reorder tool built for daily ordering fits them better.
  • Enterprise S&OP. Corporate sales and operations planning with multi-year implementations belongs in an enterprise planning suite.

How Rewize plans your stock

Rewize plans stock from the position of each SKU, set against forecast demand at each location. The position is stock on hand plus stock on order, minus reserved stock.

The sections below cover what the planner works with:

  • Days of cover
  • Health status
  • ABC classes
  • Stock per location
  • Transfer orders
  • Overstock

Days of cover per SKU

Days of cover is the number of days from today until a SKU's stock position runs short of forecast demand.

Rewize counts these orders together as stock on order:

  • Purchase orders
  • Transfer orders
  • Production orders

Every incoming unit therefore pushes that date further out.

The planner sees days of cover per SKU in the inventory overview. Rewize does not work with a fixed reorder point per SKU.

The supplier's lead time comes in through the health status. The health status compares the date the position runs short with that lead time.

Many brands start with an average of 150 to 200 days of cover. Bringing that back towards one times the supplier's lead time is often healthier and frees up cash.

Health status per SKU, from out of stock to overstock

Rewize gives every SKU one of six health statuses:

  • Out of stock
  • Overdue
  • At risk
  • Reorder
  • Healthy
  • Overstock

Each status comes from comparing the date the SKU's position runs short with the supplier's lead time. The comparison uses the rules for the SKU's ABC class.

The date the position runs short comes from the forecast per SKU and channel. That forecast comes from Rewize's inventory forecasting software.

The planner can filter the inventory list on any status, for example on At risk first. The planner then works through the SKUs that need attention before anything else.

ABC classes and availability per class

Rewize sorts SKUs into A, B and C classes by their share of revenue and reports availability per class. The ABC analysis uses revenue by default, and margin or quantity can be chosen instead. The classes come from cumulative-percentage cuts.

Tracking availability per A, B and C class shows whether the SKUs that bring in most of the revenue stay in stock.

Onewith is a size-inclusive swimwear brand with more than 300 SKUs. Onewith focused on its A-class, and that brought A-class stockouts from about 11% to about 6% through peak season.

Stock per warehouse, 3PL and marketplace pool

Rewize counts each sale at the location that shipped it. The stock need is therefore planned per location instead of as one total.

A location can be any of these:

  • The brand's own warehouse
  • A 3PL such as Monta
  • A warehouse on Picqer
  • Bol's shared FBB pool
  • An Amazon FBA pool per channel or marketplace group

Shopify orders get their location from the fulfilment, and a connected WMS attaches the location directly. The sales per location then feed the forecast and the reordering for that location. Planning across multiple warehouses and 3PLs therefore starts from what each location actually shipped.

Sales channels

  • Shopify
  • Bol
  • Amazon
Each order line is counted at its fulfilment location

Location that shipped the order

  • Own warehouse or 3PL
  • Bol FBB pool
  • Amazon FBA pool per marketplace group
Position and forecast per location

Rewize plan per location

  • Sales per location
  • Forecast per location
  • Reordering per location
Orders from Shopify, Bol and Amazon are counted at the location that shipped them, and Rewize plans stock per location.

Transfer orders between locations

Rewize counts a transfer order between locations as stock on order, and the planner decides when stock moves. Surplus at one location is never used automatically to cover a shortage at another location.

The planner moves stock with a transfer order, for example to a warehouse run on Picqer, or sets a location to restock from another location.

Overstock and the cash tied up in it

Rewize flags overstock per SKU and per location as:

  • Units
  • A ratio
  • Overstock value: the surplus units times the purchase price

A SKU already covered past the lead time plus the coverage target gets a zero quantity, so the next order adds no overstock. Cash held in overstock lengthens a brand's cash conversion cycle.

Finex Home planned 50 days of extra lead time ahead of the switch. The brand moved from air to sea freight without stockouts, saving €2 to 3 per product.

What goes into the stock plan

Rewize builds the stock plan from seven inputs. It reads them from these sources:

Input Source What it changes in the plan
Forecast per SKU and channel The Rewize forecast, or the demand plan the planner published Sets the demand the position has to cover at each location
Stock per location Picqer: stock levels.Monta: on-hand stock.Goedgepickt: on-hand stock.StockItUp: stock levels.Stockhub: on-hand stock.Odoo: stock levels. Gives the on-hand part of the position at each location
Incoming orders Purchase orders, transfer orders and production orders in Rewize Counted as stock on order, so the same units are not ordered twice
Supplier lead time The supplier's lead time in Rewize Sets when a new order would arrive, and the thresholds behind each health status
Coverage target A default setting in Rewize Sets how far past the arrival date an order covers demand; a SKU already covered gets a zero quantity
ABC class Calculated by Rewize from revenue by default, or from margin or quantity Decides which health-status rules apply, and groups availability reporting
Marketplace pools Bol: FBB stock in Bol's shared pool.Amazon: FBA stock per channel or marketplace group. Marketplace stock is planned as its own location, apart from stock you ship yourself

Across Shopify, Bol and Amazon

Rewize keeps one stock plan across the Shopify store and the marketplaces. Every sale counts at the location that shipped it.

Bol orders carry the fulfilment method on each order line. FBR sales count at the location set for the Bol channel, and FBB sales draw on Bol's shared pool.

Amazon FBA sales go to a separate pool per Amazon channel or marketplace group. That pool stays apart from orders the brand ships itself.

Where inventory planning sits in your stack

Rewize is a planning layer on top of the WMS or ERP a brand already runs. That system stays in place.

The ERP handles finance and administration, and the WMS keeps counting stock. Rewize reads the on-hand position from the WMS and calculates the quantity each SKU and location needs.

Rewize writes purchase orders back to Picqer and Exact Online.

Rewize writes inbound deliveries back to:

  • Picqer
  • ChannelDock
  • Goedgepickt
  • StockItUp
  • Stockhub
  • ShopLinkr
  • Odoo

With Monta, Rewize reads the data and writes nothing back.

Every order needs a planner's approval before it leaves Rewize, so the buyer keeps the final call.

Because the existing stack stays as it is, most brands are live within 1 to 7 days. The full list of connections is on the integrations page.

What customers got out of it

Brands with several channels and long lead times use Rewize to keep their best sellers available without adding stock:

Brand Situation Result
Solit Socks Premium socks, 107 SKUs, sold on Shopify and Bol, one supplier in Istanbul with a 1,000-unit MOQ Catalogue stockouts down from 16% to 12%, with revenue up 161% year on year in 8 months
Onewith Size-inclusive swimwear from the US, 300+ SKUs on Shopify, 30 to 90 day lead times, planning focused on the A-class A-class stockouts down from about 11% to about 6% through peak season
Hoekhome Head of Operations Alan Scanlan needed one view of stock and of when to place new purchase orders "Giving us an accurate view of our stock and when to place new POs has been game changing!"

Read all customer stories.

Forecasting, planning and purchasing in Rewize: which page do you need?

Rewize covers three related jobs, and inventory planning sits between them:

  • Inventory forecasting: the demand forecast per SKU, channel and season that the stock plan uses as its input.
  • Demand planning: the MRP add-on for brands that make or assemble their own products. It plans the raw materials behind them.
  • Purchase planning: what to buy, from which supplier and when, within each supplier's lead time, MOQ, case packs and price tiers.

Getting live

Most brands are live with Rewize within 1 to 7 days, with guided onboarding included. The Rewize team sets up the connections with you.

Pricing follows annual revenue instead of seats or SKUs, so adding team members does not change the price. The contract is monthly cancellable.

The pricing page explains the model. The ROI calculator estimates the return and payback for your own numbers.

Frequently asked questions

Holding stock ties up the cash paid for every unit that has not sold yet. That amount grows with every extra day of cover. Rewize puts a number on the part above target: overstock value per SKU and per location. That value is calculated as surplus units times the purchase price. Stock that is already over target usually has to leave through promotions or a liquidator before that cash comes back.
The Rewize MRP add-on, part of demand planning, plans the raw materials for brands that make or assemble their own products.
No. The WMS keeps track of what sits where today and handles picking. Rewize reads stock from that system and decides how much each SKU needs per location for the coming lead time.
Inventory optimisation is the word larger companies often use for much the same job. The term can also cover where stock sits within and between warehouses. Rewize treats that as part of planning: a stock plan per location, and transfer orders the planner creates. For a D2C brand buying with long lead times, the part that matters most is knowing what each location needs before the next order arrives.
Yes. Rewize reads orders, stock, products and inbound deliveries from Monta and plans the Monta location as its own location. Other warehouses and 3PLs are planned the same way when their WMS is connected, for example Picqer, Goedgepickt, StockItUp, Stockhub, ChannelDock, ShopLinkr or Odoo.
Yes. Rewize reads orders, stock, products and inbound deliveries from Bol, and orders, stock and products from Amazon. Bol FBB stock is planned as Bol's shared pool, and FBR sales count at the location set for the Bol channel. Amazon FBA stock is planned as a separate pool per Amazon channel or marketplace group. That pool stays apart from orders you ship yourself. Rewize writes nothing back to Bol or Amazon.
Rewize builds the buffer from the coverage target and the supplier's lead time. Each order is sized to cover forecast demand from the day it arrives until the coverage target date. A SKU whose position already reaches that date gets a zero quantity on the order.
Yes. Rewize reads orders, stock, products, inbound deliveries and supplier data from Picqer. Rewize counts each sale at the Picqer warehouse that shipped it. Rewize writes purchase orders and inbound deliveries back to Picqer, and nothing is sent without a planner's approval.
Yes. Rewize reads orders, stock, products and supplier data from Exact Online and writes purchase orders back to it. The planner approves each order in Rewize before it is sent.
Rewize reads orders, stock, products and inbound deliveries from Odoo and writes inbound deliveries back to it. On top of that data, Rewize forecasts demand per SKU and channel and plans the stock each location needs. Purchase advice in Rewize respects each supplier's lead time, MOQ and case packs. What Odoo's own planning features cover is described in Odoo's own documentation.