Assortment planning software built for replenishment

You assign a typology, for example basic, medium or large, to each store for a product family, and the matching products activate automatically in the stores that match, with bulk actions to apply a typology across many families at once.

You manage this from two views:

• a tag view, families across all stores in a matrix with a typology selector,
• a product view, reference by reference, with an active or inactive indicator per store.

Filtering by site, tag category or typology, saved custom views, and a hover preview of the products behind a family keep large catalogs reviewable. The active range then feeds replenishment directly, so a store only receives order proposals for products it actually carries.

Yes, that is the core of the feature. Products that are not active in a store's assortment are excluded from that store's order proposals, so buyers stop seeing and correcting lines that should never have appeared.

When a product is intentionally outside the standard matrix, you switch it on for the sites you choose as an exception, and every override is kept in a dedicated exceptions tab you can review.

Because assortment and replenishment share one engine, the assortment rule stays attached to the order, so a planner can see whether a reference is missing because it is out of range rather than because of a buffer or a supplier issue.

Enterprise merchandising suites focus on building the range: option counts, merchandise financial planning, open-to-buy, demand-driven store clustering and planogram optimization. Flowlity focuses on the store-level side, which existing products are active in which stores, and on making that range drive replenishment. It is lighter, faster to deploy and aimed at mid-market retailers and distributors rather than at enterprise merchandising teams.

If your priority is a full pre-season financial and space planning suite, those tools go deeper. If your priority is that the range you decide actually controls the orders, without a heavy implementation, that is exactly where Flowlity is strong.

That is the point. Flowlity becomes the single, shared source of truth for which products are active in which stores, so you stop chasing the latest version of a file or wondering whether every stakeholder sees the same one.

Changes are made in the app, in bulk when needed, and tracked, while product and tag lists still export to Excel or CSV when you need them elsewhere.

The difference from a spreadsheet is not just where the data lives, it is that the range is now connected to planning and controls what can be ordered.

Real assortments always have exceptions, and Flowlity treats them as first-class rather than as edits that get lost. A product that sits outside the typology matrix, for instance a seasonal item or one that only sells in certain locations such as stores near lakes or the coast, is activated manually on the exact sites you choose. Those manual activations and deactivations, whether on all sites or a selection, are recorded in a dedicated exceptions tab, so anyone can see what was overridden. Combined with tag filters that support and/or logic, this lets you build precise selections without breaking the underlying tier model.

Retailers and distributors running at least two stores with different product portfolios, especially those managing many references across store formats of different sizes and currently juggling assortment in spreadsheets or a disconnected legacy tool.

The value grows with the number of stores and the size of the catalog, because that is where manual store-by-store management breaks down and where excluding out-of-range products from orders saves the most time and cash. Retailers whose stores already fall into recognizable tiers see value fastest, since the typology model maps directly onto how they think.

The core inputs are:

• a store hierarchy with the tiers you want to manage,
• a product hierarchy of families and references,
• the sales, inventory and order data that already feeds replenishment.

You do not need a perfect dataset on day one: define the tiers, let products activate against them, then refine typologies and exceptions as you go. Because assortment plugs into planning you already run rather than a separate system, teams stand it up fast rather than through a multi-quarter transformation project. In practice, Plum Living went live on Flowlity Core in around three months, and Jolimoi was up and running on Flowlity Lite, the plug-and-play tier, in a few weeks.