Rewize integrations for D2C brands on Shopify: forecasting connected to your marketplaces, WMS and ERP

Rewize integrations read orders, stock and products from the systems a D2C brand on Shopify already runs: the shop, marketplaces such as Bol and Amazon, the WMS or 3PL, and the ERP. Rewize forecasts and plans per location. Then, wherever the integration supports it, Rewize writes the approved order back to the WMS, 3PL or ERP as a purchase order or an inbound delivery. The integration grid on this page lists every integration and its status.

Rewize is inventory forecasting and purchase planning software for D2C brands on Shopify. Because the integrations are built into Rewize, most brands are live within 1 to 7 days, with guided onboarding included. More than 100 D2C brands plan with Rewize, and Rewize holds a 5.0 rating from 31 reviews on the Shopify App Store.

Sales channels

  • ShopifyLive
  • WooCommerceLive
  • bolLive
  • AmazonLive
  • Milo POSLive

Warehouses, 3PL and ERP

  • ChannelDockLive
  • GoedgepicktLive
  • PicqerLive
  • StockItUpLive
  • StockhubLive
  • ShopLinkrLive
  • MontaLive
  • OdooLive
  • Exact OnlineLive
  • DayOneLive

AI and API

  • Claude (MCP)
  • REST API

On request

Built when a customer needs it. Ask us about yours.

Shops and marketplaces

  • Shopware
  • Magento
  • BigCommerce
  • Lightspeed
  • Zalando
  • Kaufland
  • Otto
  • MediaMarkt
  • Decathlon
  • ANWB
  • Etsy
  • eBay

Warehouses and 3PL

  • QLS
  • Byrd
  • Bigblue
  • Cubyn
  • Sendcloud

ERP and accounting

  • NetSuite
  • Qoblex
  • Business Central
  • SAP Business One
  • AFAS
  • Twinfield
  • SnelStart
  • Moneybird
  • Xero

What an inventory integration does in Rewize

An inventory integration is the connection through which a planning tool reads orders, stock per location and supplier data from another system, and writes purchase orders back to it. In Rewize, that flow has four steps.

First, Rewize reads orders and stock per location from the shop, the marketplaces and the WMS. Second, each sale counts for the location that shipped it, whichever channel it was sold on, and sales shipped from Bol LVB or Amazon FBA count for the marketplace's own pool location. Third, Rewize forecasts demand and plans purchases per location. Fourth, once a planner approves the order, Rewize sends it to the WMS, 3PL or ERP as a purchase order or an inbound delivery, depending on what that integration supports.

Shop and marketplaces

  • Shopify
  • Bol
  • Amazon
orders, stock and products

Rewize

  • Counts each sale for the location that shipped it
  • Forecasts demand per location
  • Plans purchases per location
  • Planner approves the order
approved purchase order or inbound delivery

WMS, 3PL or ERP

  • Sends stock per location and inbound deliveries to Rewize
  • Receives the approved order where the integration supports it
Rewize reads orders, stock and products from the shop and marketplaces and stock from the WMS, plans per location, and sends the approved order back to the WMS, 3PL or ERP.

The shop, the WMS and the ERP stay in place, and Rewize adds the planning layer next to them. A sale that arrives without a location still counts in the product total and the forecast, and Rewize shows it per location as "Unattributed sales".

Rewize next to your WMS's own purchase advice

Rewize forecasts per SKU, channel and location next to a WMS's own purchase advice, corrects sales history for stockout days, and applies each supplier's lead times, MOQs, case packs and closed periods. Several WMS and ERP systems offer purchase advice of their own: Picqer's purchase advice (Inkoopadvies), StockItUp's purchasing module, and Odoo's forecast with reordering rules. Monta's portal offers reporting, and its public docs do not tie that reporting to purchase advice. Brands keep their WMS, and where the integration supports it, Rewize writes the approved order back into that WMS.

Question the planner has A WMS's built-in advice Rewize
Demand per channel, including Bol and Amazon Picqer: not described in the public docs.StockItUp: uses sales data from all channels; a split per channel is not described.Monta: the portal reports units per traffic source, not tied to purchase advice.Odoo: demand comes from confirmed sales orders; a split per channel is not described. A forecast per channel and per location, with Bol and Amazon as channels. Demand is allocated to locations as single, split, geo-based or by tag.
History corrected for stockout days Picqer: looks back 4, 12 or 52 weeks; stockout correction is not described.StockItUp: sales speed corrected for trends; stockout days are not described.Monta: not described.Odoo: not described; Odoo works from confirmed orders. Automatic correction per location and channel. The corrected estimate never goes below what actually sold.
Supplier terms: lead times of 30 to 120 days, closed periods, MOQs and case packs Picqer: lead time, minimum order quantity and box size per product, plus a forecast horizon in days; closed periods are not described.StockItUp: lead time per supplier and minimum order quantity per product; case packs and closed periods are not described.Monta: not described.Odoo: vendor lead time in days, a global security lead time for weekends or holidays, a multiple quantity on the reordering rule, and a minimum quantity per vendor price. Lead time per location and per product and location. MOQ, batch size and units per order unit per product, plus supplier price tiers. A supplier's closed period pauses production time and moves the order date.
Promotions and launches Picqer: advice is adjusted by hand for a promotion; a new product is averaged from its first sale.StockItUp: not described.Monta: seasonal patterns are mentioned.Odoo: not described. Promotions sit on the marketing calendar, and a real discount raises the forecast with a damped, capped lift. A new product gets a forecast once it has sales; before that, the planner enters a manual demand plan.
Stock across several warehouses Picqer: works per warehouse, with a strategy per product per warehouse.StockItUp: minimum and maximum per location for LVB, FBA and a 3PL.Monta: not described for advice.Odoo: one reordering rule per location, with routes between warehouses. Forecast and plan per location, with each sale counted for the location that shipped it.

The middle column follows each partner's public documentation as of 20 October 2026. "Not described" means the public docs are silent on the point.

The stacks brands run with Rewize

The stack Rewize sees most often is Shopify with Bol and Amazon, frequently with Picqer as the WMS in between. The two combinations work like this:

  • Shopify, Bol and Amazon: the shop and both marketplaces feed one forecast, split per channel.
  • Shopify, Bol and Amazon with Picqer: the same three channels, with Picqer as the WMS that holds the stock per warehouse.

The integrations prospects ask about first are Shopify, Amazon and Picqer.

What brands use Rewize integrations for

Brands use Rewize integrations to plan stock held in marketplace warehouses, stock spread across several warehouses and shops, and stock that was planned in a spreadsheet or in a tool that shut down. The three cases below come from a Rewize sales call and from two Rewize customers:

  • Marketplace stock in Bol LVB and Amazon FBA. On a sales call, a brand selling on Bol raised the worry that missing or wrong channel data could distort its forecast. With the Bol and Amazon integrations connected, Rewize forecasts each marketplace as its own channel. A sale shipped from Bol LVB or Amazon FBA counts for the marketplace's own pool location, so the plan for that stock stays apart from the plan for the brand's own warehouse.
  • Several warehouses and several Shopify accounts. A bath and home brand runs a multi-warehouse setup, several Shopify accounts for its international shops and a growing supplier base. Rewize supports that purchasing flow across warehouses, Shopify accounts and suppliers, and the brand's monthly ordering time went from 3 days in Excel to 30 minutes.
  • A previous tool that shut down. A size-inclusive swimwear brand on Shopify, with more than 300 SKUs and lead times of 30 to 90 days, needed a new planning tool when its existing tool shut down and an ERP proved too heavy. Rewize plans the brand's stock from its Shopify data, and A-class stockouts fell from about 11% to about 6% through peak.

Don't see yours? Request it

Rewize builds integrations on request when a customer needs one. The On request box in the integration grid shows the systems customers have already asked for, and the Rewize team keeps adding new integrations as requests come in. To ask for one, book 30 minutes with co-founder Thijs and name the system your brand needs.

Frequently asked questions

The cost of an inventory forecasting system depends on its pricing model, and Rewize prices its plans on a brand's annual revenue. The number of users and SKUs does not change the price. Every plan can be cancelled monthly, and guided onboarding is included. The pricing page explains how the plans work.
The right inventory forecasting software depends on how often a brand reorders and how long its supplier lead times are. Rewize fits D2C brands that own their products, sell on Shopify and often on Bol or Amazon, and buy from suppliers with lead times of 30 to 90 days or more. Rewize customers range from €500K to €80M in annual revenue. Rewize is the wrong fit for resellers that reorder daily on lead times of 1 to 5 days, fashion resellers that buy once a season, and fresh produce. A brand with 15 to 20 products and €10K to €30K in monthly revenue is better off staying on Excel for now.
Excel works for inventory forecasting at 15 to 20 products on a single channel, and it is free and flexible. Past roughly 60 to 100 SKUs, once several channels are involved, or when one person is the only one who understands the file, the spreadsheet becomes hard to keep right. Olaf of Solit Socks described the turning point: "Spreadsheets worked with 27 SKUs. Then the catalogue tripled."
Rewize connects to Exact Online, and that integration is live. Rewize builds an AFAS integration on request. AFAS is listed in the On request box in the grid, and a call with co-founder Thijs is the place to ask for it.
Most brands are live with Rewize within 1 to 7 days. Guided onboarding is included, and the Rewize team sets up the connection with you.
One Rewize account can run two WMS, or a WMS and a 3PL, at the same time. Every location in Rewize has its own integration, and one account holds several locations. A WMS and a 3PL each run on their own location, and stock comes into Rewize per location from that location's integration. Rewize forecasts and plans each location on its own, and lead times can be set per location and per product and location.
Rewize has a REST API. The API reads products, sales, suppliers, purchase, transfer and production orders, shipments, demand events, bundles, bills of materials, report datasets and exports. The API can also make the same changes as the Rewize MCP server: create products, suppliers and orders, move orders through their lifecycle and mark shipments as received. The Rewize MCP server works with Rewize's own data only and does not read data from other systems. Changes made through the API or the MCP server take effect straight away. That differs from the integrations, where an order Rewize writes back waits for a planner's approval first. A connection with read-only access can never change anything. The API documentation is at api.rewize.ai/api/docs.
The Rewize forecast uses the orders, stock per location and product data that the integrations read, plus supplier data where the WMS or ERP holds it. Rewize forecasts per channel and per location, with Bol and Amazon as channels, and corrects the sales history for stockout days. A promotion on the marketing calendar raises the forecast when it carries a real discount. A new product gets a forecast once it has sales; until then, the planner enters a manual demand plan. A published manual demand plan overrides the AI forecast for the SKUs and months it covers, and the AI forecast is kept underneath. Planners can also adjust the forecast in plain language through Rey, the AI demand planner in Rewize, and every edit is a checkpoint that can be reverted.