Skip to main content
57 min readretail merchandising softwaremerchandising software

What Is Retail Merchandising Software?

Retail merchandising software is the set of systems a retailer or brand's merchandising organisation uses to decide what to sell, how much to buy, at what price, where to place it and when to mark it down, spanning merchandise financial planning, assortment planning, allocation and replenishment, pricing and markdown, and the product and space data those decisions run on.

Retail merchandising software is the set of systems a retailer or brand's merchandising organisation uses to decide what to sell, how much to buy, at what price, where to place it and when to mark it down, spanning merchandise financial planning, assortment planning, allocation and replenishment, pricing and markdown, and the product and space data those decisions run on. It is a family of systems rather than one product. Each member owns a layer of the merchandising decision at its own grain and cadence, and what makes the members a stack rather than a collection is that they read the same merchandise hierarchy, the same calendar and the same plan of record. Merchandise planning software is the member of the family this site has defined in most depth; it is not the whole of it.

This guide defines the umbrella. It covers what the category includes and what it leaves to the ERP and the point of sale; the members of the family, with the decision each owns, its grain and cadence, and the page on this site that defines it; what the overlapping phrases, merchandising software, merchandise planning software, merchandising management software, retail planning software, usually mean and which kind of page answers each; what the members have to hold in common and the seams where one hands to the next; who in a merchandising team uses which member, and how merchandising leaders use the stack to run the team; suites, point solutions, connected platforms and spreadsheets; the stack in each of ten retail verticals; the criteria for choosing; one worked example of a season's plan of record flowing from a financial envelope to a markdown decision; and the ways the stack fails. Where a member has its own guide, this one links down rather than re-defining it.

What the category covers

Merchandising, in a retailer or a brand, is the function that decides what the business will sell and how the money behind that decision is deployed. The decision has five parts, and each is a question a merchandising team answers every season and re-answers every week: what to sell, which is the assortment; how much to buy, which is the financial plan, the open-to-buy and the buy; at what price, which is the price ladder, the promotional calendar and the markdown; where to place it, which is allocation, replenishment and the store's floor; and when to mark it down, which is the exit. Retail merchandising software is the set of systems that carry those five decisions. The category is defined by the decisions, not by the departments, because the departments move between businesses: in a vertically integrated brand, merchandising sits between design and wholesale and owns the line; in a retailer, it sits between buying and stores and owns the floor; in a wholesaler, it owns the range that accounts book from. The decisions are the same in all three.

The reason to define the family as a family is that the decisions are linked and the systems that carry them were, for a long time, bought separately. The financial plan constrains the assortment; the assortment is what allocation distributes; the price the assortment was planned at is what the markdown reduces; the floor the space plan lays out is the ceiling on how many options a store can carry. In a business that runs on workbooks, every one of those links is a person carrying a number from one file to another, and the replace spreadsheets page sets out what that costs. In a business that has bought its systems one at a time, the links are integrations, and the integrations are where the plan drifts. The value of the stack is in the seams, which is why this guide spends as long on what the members share as on what each member does.

Two things sit outside the category and are searched for alongside it. The ERP, or in a retailer the merchandise management system, records what has happened: the order placed, the goods received, the stock on hand, the sale rung and the ledger value of inventory. The point of sale records the transaction at the register and, with the ERP, holds the store's stock position. Both are systems of record for transactions, every member of the merchandising family reads from them, and none of the members replaces them. The boundary is the one supply chain software vs merchandise planning software draws for the planning core: merchandising software decides what the business intends; the ERP and the point of sale record what it did. The discipline the software serves, as distinct from the software, is defined in what is merchandise planning? and in the glossary entry on merchandising planning; the glossary's merchandising operating system entry names the connected form of the stack.

The members of the family

The table lists the members as a buyer meets them, with the decision each owns, the grain and cadence it works at, and the page on this site that defines it. The subsections that follow say what each contributes to the whole and where it hands on; they do not repeat the definitions.

MemberThe decision it ownsGrain and cadenceDefined on
Merchandise financial planning and open-to-buyHow much to sell, at what margin, holding how much stock; how much can be received each periodDepartment and class, in dollars, by month or week; set a season ahead, reforecast through the seasonWhat is merchandise planning software?, what is open-to-buy planning?
Assortment and range planningWhich options to carry, for which channels and clusters, how deepStyle and style-color by cluster and delivery; once a season, re-cut in seasonWhat is assortment planning software?
Item, buy and size planningHow many units of each option, by size and pack, from whom, landing whenStyle-color and SKU; per delivery, by lead timeWhat is merchandise planning software?, the buy and size modules
Allocation and replenishmentWhich doors and channels get which units, and how continuing items are refilledSKU by door by week; weekly or dailyWhat is retail allocation software?
Pricing and markdown optimizationThe price ladder, promotions, and when, how deep and where to mark downItem by price zone or channel by week; a weekly markdown cadenceMarkdown optimization strategies
Space and visual merchandisingHow much floor and fixture each category and item gets, and how it is presentedFixture by store, by floor set or resetSpace planning vs merchandise planning
Product information and PLMThe product record: hierarchy placement, attributes, colorways, costs, imagesStyle and style-color; continuousProduct data, data readiness for merchandise planning
Merchandising analytics and reportingWhat happened, read against the plan, at any grainAny grain; daily and weekly, with a season-end hindsightFrom reporting to decisions in planning

The first four rows are the planning core, and they are what merchandise planning software covers when it is bought as one connected system: the financial plan, the open-to-buy, the assortment, the buy, size and pack, allocation and the in-season reforecast, with the markdown calendar it books against the planned reductions line, on one data model. The remaining four are the members that sit around the core, and a business can have excellent planning software and still have its pricing, its floor, its product record and its reporting in systems that do not read the plan. A merchandising stack is complete when every one of these decisions is made against the same plan of record, whichever products the decisions are made in.

Merchandise financial planning and open-to-buy

The financial plan is the frame everything else has to add up to: sales, margin, inventory and the turn they imply, by department and period, planned top-down and reconciled against a bottom-up build. The open-to-buy converts the frame into money that can be received each period. What the member contributes to the family is the envelope: every option the assortment carries, every unit the buy commits and every markdown the pricing member takes is spent against it. The merchandise financial plan, open-to-buy and WSSI entries carry the arithmetic; the OTB planning page describes the open-to-buy as a live workflow.

Assortment and range planning

The assortment is the plan denominated in options: how many styles and style-colors in each class and price tier, for which channels and store clusters, at what depth and planned exit; range planning is the same decision seen from the wholesale side. What the member contributes is the translation of a dollar envelope into things that can be bought, and the grid by cluster and channel that every downstream member reads as a target. What is assortment planning software? defines the member in full; what is assortment planning? covers the discipline; line planning vs assortment planning draws the boundary with design's line.

Item, buy and size planning

The buy turns options into quantities, costs, vendors and delivery dates, and size and pack planning decide how each buy is split by size and packed. It is the first layer that becomes a commitment outside the business, because the purchase order is built from it, and what it contributes to the family is the handoff to the factory and the ERP: the buy goes out as purchase orders with its size breakdown and channel split intact, and the receipts come back as actuals the open-to-buy relieves. The buy planning page describes the member; size and pack optimization covers the size arithmetic; buy planning and size curve are the terms.

Allocation and replenishment

Allocation decides which doors and channels receive which units, pre-season and as receipts land; replenishment decides how continuing items are refilled against a target stock or a rate of sale. What the member contributes is the finest grain in the family, SKU by door by week, and with it the earliest read on whether the plan is working, because a door selling out of a size is visible here weeks before it shows in the class-level reforecast. What is retail allocation software? defines the member; allocation and replenishment best practices and store clustering for apparel cover the practice; the allocation page describes the product; allocation optimization and replenishment are the terms.

Pricing and markdown optimization

Pricing decides the ticket price of each item, by zone or channel, and the promotional calendar that moves it temporarily; markdown decides when a price is reduced permanently, how deep and where, to clear stock the plan does not want to carry past its season. What the member contributes is the recovery of the plan's margin when sell-through runs behind: the markdown is booked against the planned reductions line the financial plan assumed, and a markdown taken without reading that line is a decision made against no target. Markdown planning, the calendar of reductions booked against the plan, sits inside the core; markdown optimization, the price-elasticity engine that recommends when and how deep, sits at its edge, because it is a pricing decision rather than a quantity decision and a core bought to decide quantities can leave it out, and that gap is one of the failure modes at the end of this guide. Markdown optimization strategies covers the method; dynamic pricing for fashion and price elasticity and promotion planning by vertical cover the pricing side; markdown optimization, markdown cadence and pricing intelligence are the terms.

Space and visual merchandising

Space planning decides how much floor and fixture each category gets in each store and where each item sits on the fixture; visual merchandising decides how it is presented, in floor sets that change on a calendar. What the member contributes is the physical ceiling on the plan: a store's fixture capacity is the upper bound on the options a cluster can carry and the depth a door can hold, and space planning vs merchandise planning sets out how that ceiling is read into the plan rather than discovered at floor set. One distinction prevents a recurring confusion: the visual boards on which design and merchandising review a line, described on the visual line page, are a planning tool for the assortment; store visual merchandising is the presentation of what the assortment decided.

Product information and PLM

Every member plans against a product record: where the style sits in the hierarchy, its attributes, colorways, cost versions and images. The record is mastered somewhere, in a PLM, a product information system or the planning system's own product module, and the member's contribution is that the record is maintained once and read everywhere, so the silhouette attribute the assortment rolls up by is the attribute the pricing member segments by and the analytics member reports on. The product data page describes that record; data readiness for merchandise planning sets out what has to be true of the hierarchy and attributes before any other member can work; the retail data model entry describes the structure the members share.

Merchandising analytics and reporting

The reporting layer shows what happened, by style, door and week, and the season-end hindsight reads a whole season against its plan to shape the next. What the member contributes depends on whether it reads the plan of record: a dashboard that shows a style behind plan is reading a plan that lives somewhere, and if that somewhere is a file the dashboard reports against a number nobody can change. Reporting that lives inside the planning members, where actuals are read against the plan at the grain the decisions were made, is part of the stack; reporting beside it is a mirror. From reporting to decisions in planning argues the point; how to hindsight a season covers the season-end read; the intelligence page describes in-season performance and hindsight built into where planning decisions happen; retail analytics and hindsight analysis are the terms.

Demand forecasting and demand sensing: the signal the members read

One more class of system is sold into the family and belongs beside it rather than in it. Demand forecasting projects how much of an existing item will sell, usually at item-location-week grain; demand sensing is the same read made more often, from fresher signals. Neither decides what to carry or how much money to put behind it; both feed members that do, as the baseline the replenishment member reorders against and the reforecast the planner adjusts, and both are weakest on a new option with no history. What is demand sensing software? defines the neighbouring category; demand planning vs merchandise planning separates the disciplines.

Merchandising software, merchandise planning software, merchandising management software, retail planning software

A search for this category returns five or six phrases that overlap without coinciding, and a buyer who does not know which phrase they mean will evaluate the wrong class of product. The confusion has a mechanism: the word merchandising names a department, a discipline and a class of system, and vendors name products by the broadest word that describes them. The table says what each phrase usually means and which kind of page answers it. Usage varies by business and by vendor, so the table describes how the phrases are commonly used rather than legislating them.

PhraseWhat it usually meansWhich page type answers it
Retail merchandising software, merchandising softwareThe whole family: the systems a merchandising organisation runs, from the financial plan to the markdownA category definition such as this guide; a best-of page such as best merchandising software for apparel ranks products inside the category rather than defining it
Merchandise planning software, merchandising planning softwareThe planning core: financial plan, open-to-buy, assortment, buy, size and pack, allocation and in-season reforecast on one data modelWhat is merchandise planning software? defines it; the merchandising planning page is a product page inside it
Merchandising management softwareTwo things. In retail systems vocabulary, the merchandise management system, the transactional core that holds the item master, purchasing, inventory and price execution; in a buyer's search, the software a merchandising leader uses to manage the team's calendar, plan of record and reviewsThe first meaning is an ERP question; the second is answered in the section on how merchandising leaders use the software, below
Software for managing merchandising teamsThe leader's use of the stack: one plan of record, a shared calendar, reviews run from the same numbers, decision rights by layerThe same section of this guide and the merchandising leaders page
Retail planning softwareThe members a retailer's planning department runs, usually merchandise financial planning, assortment and allocation; in some vendors' usage it stretches to store operations planning such as labour scheduling, which is a different disciplineThis guide for the family; what is merchandise planning software? for the core
Store planning softwareSpace and floor planning: fixture layout, planograms, capacity by storeSpace planning vs merchandise planning
Assortment planning software, allocation software, markdown optimization softwareOne member eachWhat is assortment planning software?, what is retail allocation software?, markdown optimization strategies
ERP, merchandise management system, point of saleThe transaction record: orders, receipts, stock, sales, the ledger; the registerNot members of the family; every member reads from them. Supply chain software vs merchandise planning software draws the line
Demand planning software, demand sensing softwareForecasting how much of an existing item will sell, and how fast that read updatesWhat is demand sensing software?

Two of the rows deserve a paragraph.

Merchandising software and merchandise planning software are nested, not synonymous. Merchandise planning software is the planning core; merchandising software is the core plus the pricing, space, product data and reporting members around it. A product page that calls itself merchandising planning software is making the narrower claim, and a buyer who needs markdown optimization or planogramming should not expect to find them there unless the page says so. The reverse error is the mirror of it: a best-of list of merchandising software that ranks only planning products is ranking one member and calling it the family.

Merchandising management software is a phrase with two owners. In retail systems vocabulary it is the transactional core, which holds the item master, purchase orders, receipts, inventory and price execution and does not plan; to a merchandising leader searching for a way to run a team, it is the system that holds the plan of record, the calendar and the reviews. The test for which one a product is, is whether a planner can change a forward number in it or only read a past one. The merchandising planning glossary entry defines the discipline the planning members serve, deciding what to buy, in what quantity, at what price and margin, for when and through which channels, held against a financial plan as the season sells; retail planning, in its merchandising sense, names that same discipline.

What the members have to hold in common

A merchandising stack is one system to the extent that its members share the objects below. A business can own one product for every row of the members table and still have no stack, if each product holds its own copy of the hierarchy and its own version of the plan; and a business can run two or three products and have a real stack, if those products read the same objects. The table lists the shared objects, who usually masters each, which members read it, and what breaks when two members hold different copies. The failure column is the one to read first, because it is where the reconciliation work in a merchandising team actually comes from.

Shared objectWhat it isWho masters itWhat breaks when two copies differ
Merchandise hierarchyDivision, department, class, subclass, style, style-color, SKUThe product record, with the ERP as the transaction treeA class planned in one tree and sold in another cannot be read against plan; the reforecast is built on mis-attributed actuals
CalendarRetail weeks on a 4-5-4 or 4-4-5 structure, seasons, deliveries, reset datesThe planning coreSales phased on one calendar and reported on another show a variance that is a date, not a miss
Product attributesSilhouette, fabrication, color family, fit, finish, shade, licence, material, size systemThe product recordAttributes held as text in one member and as dimensions in another cannot be rolled up together, so the mix is judged by eye
Locations and clustersChannels, regions, store clusters and grades, door capacitiesThe planning core, with the ERP's location listA grid built on one cluster definition and allocated on another puts depth where the plan did not put it
Price ladder and zonesPrice tiers, ticket prices, price zones, the promotional calendarThe pricing member, read by the financial plan and the assortmentA markdown taken against a price the plan did not carry breaks the margin roll-up and the reductions line
Plan of recordThe current approved version of each layer, and the history of versions behind itThe planning coreTwo versions in two systems, and a meeting spent agreeing which is right before any decision is made
ActualsSales, stock, receipts and on-order, by SKU by door by weekThe ERP and the channels, read onceEach member reconciles to the ERP on its own and the plan is compared with three different actuals

The hierarchy and the plan of record are the two that decide whether the rest can be shared at all. The merchandise hierarchy is the tree every member plans at some level of and rolls up or spreads down through, and merchandise hierarchy by vertical shows how differently that tree is shaped from one vertical to the next. The plan of record is harder to specify, because it is an agreement rather than a feature: that, at any moment, there is one current approved version of the financial plan, one of the assortment, one of the allocation and one of the price ladder, that every member reads that version, and that changes to it are made in one place by the role that owns the layer. A workbook stack has no plan of record because every author has a version; an assembled stack has one only if the integrations carry versions as well as numbers.

The seams: plan to assortment to allocation to pricing

The members hand to one another in a sequence, and each handoff passes something down and sends something back. The seams are where a stack is either connected or merely adjacent, so they are the places to test.

From the financial plan to the assortment, what passes down is the envelope: planned receipts by class, tier, channel and period, at the planned ticket. What comes back is spend: every option the assortment funds, at its depth and ticket, is receipts against the envelope, and the open-to-buy position should move as the option count moves. The test is to revise the envelope while the assortment is open and see whether the grid knows.

From the assortment to allocation, what passes down is the grid: options by cluster and channel, with the depth per cell and the size and pack profile behind it. What comes back is the door-level read: which doors are selling out of which sizes, which have stock the plan did not expect to sit, and therefore where the next receipt and the replenishment should go. The test is to change a cluster definition in the assortment and see whether the allocation's targets follow.

From allocation to pricing, what passes down is the position: sell-through, weeks of supply and stock by item by door, read against the planned exit. What comes back is the markdown: a permanent price change, booked against the planned reductions line, that changes the rate of sale the allocation and the reforecast now plan against. The test is to take a markdown on one item and see whether the open-to-buy's reductions line, the reforecast and the allocation's weeks of supply all read the new price.

And from every member back to the financial plan, what comes back is the reforecast: the season re-planned with actuals in it, which resets the envelope for the periods still open and starts the sequence again. The in-season chase and how often to reforecast cover that loop; the glossary entry on connected planning names the property a stack has when the seams carry the changes without a person carrying them.

Who in a merchandising team uses which member

Each role in a merchandising organisation lives in a different member, and a stack is experienced by each role as the view it opens in the morning. Role names move between businesses, and in a smaller brand two or three of these roles sit in one chair, but the views are stable. The table gives the daily home of each role, what it opens, and what it hands on to the next role; the merchandising leader's row is expanded in the section that follows, because it is the role the phrase software for managing merchandising teams is about.

RoleLives inOpensHands on
Merchandise plannerFinancial planning and open-to-buy; the in-season reforecastPlan against actuals by class and month; receipt budget by period; the stock-to-sales positionThe envelope the buyer spends, and the reforecast every other member re-plans to
Buyer or merchandiserAssortment and range planning; item and buy planningThe line by class and tier; option count against the frame; depth, vendor, cost and delivery per optionA funded, sized buy to the allocator and the factory; the range to the wholesale team
Allocator or replenishment analystAllocation and replenishmentStock and sales by door and SKU; receipts landing this week; the grid; replenishment triggersUnits in doors; transfers; refills; the door-level read that feeds the markdown and the reforecast
Pricing analyst or markdown plannerPricing and markdown optimizationSell-through and weeks of supply by item; the price ladder and zones; the reductions line against planMarkdown and promotional decisions, booked against planned reductions
Visual merchandiser or space plannerSpace and visual merchandisingFixture capacity by store; planograms; the floor set and reset calendarThe ceiling on options per cluster; the presentation the allocation fills
Merchandising operations or product dataProduct information and PLM; the hierarchyThe product record; attribute dictionaries; the hierarchy treeA clean record every other member plans on
Merchandising leaderEvery member, at summary grainThe plan of record against actuals; the calendar; the review agenda; who owns which layerDecisions, approvals, and the exceptions the team works this week

The handoffs in the last column are the places a workbook stack breaks and an assembled stack has to be integrated: the planner's envelope and the buyer's buy, the buyer's size profile and the allocator's curve, the allocator's weeks of supply and the pricing analyst's markdown, the space planner's capacity and the merchandiser's option count. What is merchandise planning software? describes the planner, buyer, allocator, merchandiser, finance and design views of the planning core in more detail; this guide adds the pricing, space and product-data roles that the wider family brings in, and the leader.

How merchandising leaders use the software to run the team

The query behind this section is a real one, and it deserves a plain answer. A merchandising leader, a VP of merchandising, a general merchandise manager, a planning director, does not spend the day in any one member of the stack. The leader uses the stack to run the team, and runs it through four things the software either holds or does not: the calendar, the plan of record, the reviews and the decision rights. A stack that cannot hold those four forces the leader to run the team from a side file, and the side file becomes the plan.

The calendar is the sequence of milestones a season runs on: the hindsight of the last season, the lock of the financial plan, the line review, the assortment sign-off, the buy commit, the allocation, the weekly trade meeting once the season opens, the reforecast, and the markdown reviews. In a connected stack the calendar is a property of the plan rather than a document beside it, so that each layer's version is dated against its milestone and the leader can see which layers are locked, which are open and which are late. Planning calendar by vertical sets out how the sequence differs between verticals, and the time and action calendar covers the production side of the same clock.

The plan of record is the single current approved version of each layer. The leader's use of it is simple to state and hard to get from a workbook stack: when the leader opens the plan, the number on the screen is the current number, and the question in the room is about the decision rather than about which file is right. A stack holds a plan of record when it carries versions, when a change to a layer is made by the role that owns the layer and visible to everyone else at once, and when a prior version can be opened to see what was approved and when it changed. The glossary entry on planning workflow automation describes the mechanics; planning governance describes the practice.

The reviews are where the leader's time goes, and each one reads a different member at a different grain. The table lists the recurring ones.

ReviewCadenceReadsThe decision taken
Financial plan reviewOnce a season, then at each reforecastThe financial plan against the budget and the last season's actualsLock the frame; set the envelope by department and period
Line and assortment reviewOnce a season, by deliveryThe assortment against the envelope and the attribute targetsSign off the option count, depth and grid; release the buy
Open-to-buy reviewMonthly, weekly in seasonReceipts committed and landed against the envelope; the stock-to-sales positionRelease, hold or cancel receipts; move budget between classes
Weekly trade meetingWeekly in seasonSell-through, stock and weeks of supply by class and item, against planChase, cut, transfer, reprice; which exceptions the team works this week
Markdown reviewWeekly or fortnightly in seasonItems behind their planned exit; the reductions line against planWhich items to mark down, how deep, where, and what it costs the margin plan
Season hindsightOnce a seasonThe whole season against its plan, by class, option, door and weekWhat the next plan keeps, changes and stops

The weekly trade meeting is the review that most exposes whether the stack is connected, because it reads every member at once: the planner's reforecast, the allocator's door-level position, the pricing analyst's candidates for markdown and the buyer's chase options, all for the same week. The weekly trade meeting sets out how it is run from one plan; in a workbook stack it is run from four extracts and the numbers have to be agreed before the decision can start.

Decision rights are the fourth thing. Which role may change which layer, what needs the leader's approval, what is locked once committed, and what the exception process is when a buyer needs to break the envelope or an allocator needs to override the grid. In a connected stack these are permissions and workflow states; in a workbook stack they are a convention that holds until someone is away. The leader's working question each week, which exceptions does the team look at first, is the one the analytics member exists to answer: a stack that surfaces the styles, doors and weeks that have moved away from plan puts the team's attention where it is needed, and one that does not leaves the leader to find them by reading every row. The merchandising leaders page describes what the role needs from a planning system; decomposing a plan miss describes how a leader reads a variance once the team has found it.

Suites, point solutions, connected platforms and spreadsheets

The family is packaged in four ways, and a buyer searching for merchandising software options is usually choosing between packagings before choosing between products. The descriptions below are mechanical rather than promotional: each packaging is the right answer for some businesses, and the table says what each gives, what it trades and when it fits. No vendor is named, because the trade-offs belong to the packaging rather than to any product.

PackagingWhat you getWhat you tradeFits when
A suiteSeveral members from one vendor on one data model, usually alongside the ERP or the supply chain stackPlanning depth sized for the suite's general customer; a rollout scoped as its own programme; the vertical grain configured onto a generic model rather than native to itThe business already runs the suite and has the team to configure and maintain it
Point solutions, assembledThe deepest available tool for each member, chosen one at a timeEvery seam is an integration the buyer owns; the hierarchy, calendar and cluster definitions have to be kept identical in each system by handPain is concentrated in one or two members and the rest are well served
A connected planning platform, with point members attachedThe planning core on one data model, with pricing, space or analytics attached where the business needs themIntegration on both sides, to the product record above and the transaction record below; a new system rather than a module of an existing onePain is reconciliation between the planning layers and the grain is vertical
SpreadsheetsEvery member, built by the people who use them, at no licence costThe seams: every link between layers is a person carrying a number; one version per author; no concurrency; the plan stops when its author is awayA business whose layers have not yet separated into different hands

The variable that decides between them is where the reconciliation pain sits, not the size of the business. A suite buys governance and a shared transaction record and pays in planning depth and in a rollout whose duration is set in a statement of work. Assembled point solutions buy depth in each member and pay at every seam, because the hierarchy change that takes an afternoon in one system has to be made again in four. A connected platform buys the seams inside the planning core and pays in the two integrations at its edges, up to the product record and down to the ERP, with pricing and space attached where they are needed rather than built in. Spreadsheets cost nothing to licence, and the price is paid by the people who carry the numbers between them. What is merchandise planning software? describes the three software architectures of the planning core; build vs. buy planning software covers building the stack internally; how to evaluate the implementation model covers who implements and maintains each, which follows the packaging more closely than the vendor.

The merchandising stack by vertical

The members are the same in every retail vertical. What differs is which members carry the weight of the decision, the grain each works at, the clock the season runs on and the constraint that binds the plan. A stack that does not carry a vertical's grain natively pushes that vertical's planners into a spreadsheet beside it, which recreates the problem the stack was bought to solve. Each paragraph below says what the stack looks like for one vertical; each vertical has its own planning guide for the discipline.

Apparel

Apparel's stack is the full family at full weight. The financial plan and open-to-buy run by season, with carry-forward stock between seasons and delivery drops inside each; the assortment plans at style and style-color by collection and fabrication as well as by class, with a size curve by class and cluster behind every option; the buy splits across DTC, wholesale and stores and is bound upstream by fabric minimums on the colorway count; allocation distributes by size within style-color across clusters; the markdown member runs a weekly cadence against a planned exit for every seasonal option; and the product record carries silhouette, fabrication, fit and colorway as planning dimensions. Planning against fabric minimums covers the binding constraint; the apparel brands page sets out the apparel case; the style-color matrix is the grain.

Footwear

Footwear's stack is built around the size run. A model-color is bought as a run across sizes, half sizes and, where the model offers them, widths, so the allocation and replenishment member carries more of the decision than it does in apparel: size-run completeness by door is the presentation minimum, replenishment refills by size within width, and a cut to depth is a decision about which sizes to drop rather than a percentage. The assortment member carries the model year beside the season, because carryover models continue across seasons and the changeover is a planned exit; the markdown member treats the broken run, not the slow model, as the signal. Assortment planning for footwear brands covers the run arithmetic; see also the footwear brands page.

Accessories and bags

Accessories' stack is built around the colorway and the hardware finish rather than the size, so the product record carries more of the weight: colorway and finish have to be attributes every member rolls up by. The assortment is layered, with an evergreen core that carries forward and replenishes on a rule beneath a seasonal layer bought once around a hero color, so the replenishment member runs for the core while the markdown member runs for the seasonal layer, and the two have to read the same item differently. Attach rate, the rate at which an accessory sells with a garment or a shoe, is a planning input the analytics member has to surface. Planning accessories lines covers the hero-color arithmetic; see also the accessories brands page.

Home and furniture

Home and furniture's stack is built around the long lead time. SKUs are committed a season or more ahead and shipped by ocean in containers whose minimum can set the buy rather than the option's demand, so the financial plan and open-to-buy run on a longer horizon and the buy member has to hold the container as a constraint. Options multiply as a frame in several finishes, fabrics or sizes without multiplying the floor sample, so the space and visual member carries the floor set as a real decision: which options are shown as vignettes, which are stocked and which are special order. Dealer prebooks written at market are netted against the buy, and landed cost moves with freight, so the margin the plan is built on has to be re-read from logistics actuals. Merchandise planning for home and furniture brands covers the mechanics; see also the home and furniture brands page.

Outdoor

Outdoor's stack is built around the dealer prebook and the model year. The assortment is set twice, once as the range dealers book from at a sales meeting months before delivery and again as the production buy sized from the prebook, with at-once stock held back for fill-in; the buy member has to hold the prebook position against the buy, and the replenishment member runs the at-once stock. The line mixes soft goods sized like apparel with hard goods that have sizes of their own or none, so two option grains sit in one plan, and the model year carries carryover models across seasons with the changeover planned as an exit. Weather drives the in-season read more than the calendar does. Merchandise planning for outdoor brands covers the model-year rhythm; planning a model year changeover covers the exit; see also the outdoor brands page.

Sporting goods

Sporting goods' stack runs several seasons at once, one per sport, each with its own start, peak and end, so the financial plan and open-to-buy are phased by sport rather than by one retail calendar, and the assortment is a set of sport-specific ranges that share a store but not a season. Prebook from team and institutional accounts sits beside retail demand for the same items, hardgoods carry their own size systems, racquet grips, bat lengths, boot sizes, beside softgoods with apparel sizing, and the markdown member works against a window that does not move for a sport that starts on a fixed date. Merchandise planning for sporting goods brands covers the multi-season structure; see also the sporting goods brands page.

Beauty

Beauty's stack is built around the shade ladder, the retailer's planogram and replenishment. A foundation in dozens of shades or a lip color in a dozen is bought and replenished as a set, because a missing shade reads to the customer as the product being unavailable, so the replenishment member carries most of the weight and the assortment member moves depth within the ladder rather than cutting shades out of it. At retail partners the listing is planogram-driven, so the space member is partly the retailer's: gondola reset dates set when a range can change on shelf and facings per door set the fixture capacity. Shelf-life dating, less the remaining life the retailer requires at delivery, is a ceiling on depth for slow shades that the stack reads from the batch system rather than owns, and launches are planned as events with a pipeline fill. Merchandise planning for health and beauty brands covers shade-range planning; see also the health and beauty brands page.

Toys and games

Toys' stack is built around the gifting peak and the licensed window. Demand concentrates in a few weeks at the end of the year, so the financial plan and open-to-buy are shaped by those weeks and the buy is committed far ahead of them with little chance to chase; the markdown member's exit is planned into the buy rather than discovered in January. Licensed product runs in windows tied to a film or a franchise, with a start and an end the brand does not control and royalty terms that change the margin, so the product record carries the property and the window as attributes with their own exit, and the space member plans depth in case packs so that a door's facing is filled in whole cases. Merchandise planning for toy and game brands covers the peak; planning a licensed product window covers the window; see also the toys and games brands page.

Baby and juvenile

Baby and juvenile's stack is built around registry demand and replenishment. A part of the demand for a car seat, a crib or a stroller is visible months ahead through the registry in a way few other verticals enjoy, so the financial plan and the allocation read a committed-demand signal the analytics member has to carry; a part is replenished on a steady rate because the product is consumed as the child grows, so the replenishment member runs core items natively. Size is a stage range rather than a body measurement, the product record carries certification on a base that cannot change without re-certification, and a safety recall can remove an item from sale in a day and leave a hole in the grid, the open-to-buy and the registry promise at once. Merchandise planning for baby and juvenile brands covers registry demand; planning with registry demand covers the mechanism; see also the baby and juvenile brands page.

Jewelry and watches

Jewelry and watches' stack is built around a precious-metal cost base that moves between the plan and the sale, so the financial plan's margin has to be re-read against the metal price and the product record has to carry metal and stone content as cost drivers. The turn is slow, with pieces carried across seasons and model years rather than cleared at the end of one, so the markdown member has to hold low depth across many SKUs without reading slow turn as a markdown signal, and the allocation member places pieces door by door, because a piece's presence in a door is a security and a presentation decision as well as a demand one. Gifting peaks concentrate demand. Merchandise planning for jewelry and watch brands covers the cost base; planning margin on a moving cost base covers the re-read; see also the jewelry and watch brands page.

The pattern across the ten is the one the member guides name: the vertical sets the grain, and the stack either carries that grain natively or pushes it back into a spreadsheet. A buyer evaluating the family should test the stack on their own object, pairs by size within width, a shade ladder as a set, a frame in four finishes, a licensed window with its exit, before any other feature is looked at.

Selection criteria and the questions to ask

Four companion guides cover the evaluation of planning software in depth, and this section does not repeat them. How to choose apparel planning software sets out a six-step process from defining the problem to evaluating how sell-through data gets in; questions to ask planning software vendors gives five question families that do most of the qualification work; build vs. buy planning software covers the internal option; how to evaluate the implementation model prices who configures and maintains the system for the life of the contract. What this guide adds is the criteria that belong to the family rather than to any member: the ones that test whether a set of products is a stack. Every one of them is a test of a seam or a shared object, and each can be asked of a suite, an assembled set of point solutions or a connected platform in the same words.

CriterionWhat to look forThe question that tests it
One hierarchyEvery member plans on the same merchandise hierarchy, mastered once"Add a subclass. Where do I add it, and which systems know an hour later?"
One calendarRetail weeks, seasons, deliveries and reset dates shared by every member"Move a delivery two weeks. What moves with it, in which systems?"
Attributes as dimensionsProduct attributes held once and rolled up by every member"Show me the better-tier share in the assortment, in the markdown candidates and in the hindsight, from the same attribute"
One cluster definitionStore clusters and grades shared by the assortment, the allocation and the space plan"Move four doors to another cluster. Does the grid, the allocation and the fixture capacity all follow?"
A plan of recordVersions, approvals and locks on each layer, visible to every member"Open last month's approved assortment next to today's. Who changed what, and when?"
The envelope seamThe open-to-buy read live by the assortment, with spend pushed back"Cut the envelope by a tenth while the grid is open. What changes, and where do I see it?"
The grid seamThe assortment grid read by allocation as a target"Change an option's cluster placement. What does the allocator receive?"
The markdown seamA markdown booked against the planned reductions line, read by the reforecast and the allocation"Take a markdown on one item. Show me the reductions line, the reforecast and the weeks of supply afterwards"
Actuals read onceSales, stock and receipts read from the transaction record into every member from one feed"Where does each system get its actuals, and how often do they disagree?"
The vertical grainThe object the business actually plans, carried natively"Plan pairs by size within width", or "plan a shade ladder as a set", or "plan a frame in four finishes"
The leader's viewCalendar, plan of record, review agenda and decision rights in the system"Run next Monday's trade meeting from the system. What do I open, and what do I have to bring from elsewhere?"
Who changes it laterWho adds a hierarchy level, a cluster or an attribute a year after go-live, and what it costs"A year in, we restructure the hierarchy. Who does the work, and what is the quote?"

The best-of pages on this site, best merchandising software for apparel, best apparel planning software and best assortment planning tools, compare products against criteria like these inside the category, and the software buying guides hub collects them; the vendor comparisons go head to head against named products. A buyer who has read this far should take the criteria above into those pages rather than the other way round, because a best-of list is only useful once the buyer knows which member, or which packaging, is being ranked.

A worked example: one season's plan of record through the members

The arithmetic below follows a single class, women's sweaters in a store channel, from the financial envelope through the assortment and the allocation to a markdown decision in week eight of a sixteen-week season. Every figure is illustrative, chosen so the division comes out cleanly; none is a benchmark, and a real class would carry a price ladder rather than one ticket. The point is the shape of the flow: each member takes the number the member above it produced, and the components at every step sum to the step before.

Step 1: the financial plan sets the envelope

The planner's season plan for the class, at retail, holds planned sales of $600,000, planned markdowns of $90,000 (fifteen percent of planned sales), planned end-of-season stock of $144,000, beginning-of-season stock of $114,000 and nothing yet on order. The open-to-buy is the receipts the plan needs:

LineAmount at retail
Planned sales$600,000
Planned markdowns$90,000
Planned end-of-season stock$144,000
Less beginning-of-season stock($114,000)
Less on order$0
Receipts needed, the open-to-buy$720,000

The check that the plan closes in units as well as dollars uses a single planned ticket of $80 for the class. Receipts of $720,000 are 9,000 units; beginning stock of $114,000 is 1,425 units; end-of-season stock of $144,000 is 1,800 units. Units sold are therefore 1,425 plus 9,000 less 1,800, which is 8,625 units, and 8,625 units at the $80 original ticket is $690,000, which is planned sales of $600,000 plus planned markdowns of $90,000. The envelope the assortment receives is 9,000 units, or $720,000 at ticket, and the reductions line it will later be measured against is $90,000.

Step 2: the assortment turns the envelope into options and depth

The buyer plans the class into two store clusters: cluster A, 40 large doors that carry the full size range, and cluster B, 20 small doors that carry the core sizes only. The presentation minimum is one complete curve per door per option: in cluster A the six-size curve XS 1, S 2, M 3, L 3, XL 2, XXL 1, which is 12 units; in cluster B the three core sizes S 2, M 2, L 2, which is 6 units. The plan holds a distribution-centre reserve of one quarter of each option's floor set to refill core sizes once during the delivery.

LineCalculationResult
Floor set per option, cluster A40 doors × 12 units480 units
Floor set per option, cluster B20 doors × 6 units120 units
Floor set per option, total480 + 120600 units
Reserve per option600 ÷ 4150 units
Planned depth per option600 + 150750 units
Options funded9,000 ÷ 75012 options
Units used12 × 7509,000 units
Spend against the envelope9,000 × $80$720,000

Twelve options at 750 units spend the envelope to the unit. The buyer splits them as four core carryover styles and eight seasonal styles, and the eight seasonal options are planned to exit the season at ninety percent sell-through, 675 of 750 units sold, leaving 75 units each for the final clearance. The assortment hands the allocation member a grid, twelve options by two clusters with the depth per cell above, and hands the buy member twelve buys of 750 units each with the size profile the curves imply.

Step 3: the allocation distributes the grid

The allocator reads the grid as the target and distributes the receipts as they land. At launch, each option's floor set goes to the doors and the reserve is held at the distribution centre.

LineCalculationResult
Launch allocation, cluster A12 options × 480 units5,760 units
Launch allocation, cluster B12 options × 120 units1,440 units
Launch allocation, total5,760 + 1,4407,200 units
Per door, cluster A12 options × 12 units144 units
Per door, cluster B12 options × 6 units72 units
Reserve held at the distribution centre12 options × 150 units1,800 units
Total7,200 + 1,8009,000 units

The checks run both ways: 40 doors at 144 units is 5,760 and 20 doors at 72 units is 1,440; the launch allocation of 7,200 units is $576,000 at ticket and the reserve of 1,800 units is $144,000, and together they are the $720,000 the envelope allowed. Nothing has been lost or invented between the three members, which is the property a connected stack has by construction and a workbook stack has only when every re-key is checked.

Step 4: the markdown decision reads the plan's margin target

In week eight, the allocator's door-level read shows one seasonal option, call it option nine, selling behind plan. The plan expected 360 units sold by week eight, 45 a week; the option has sold 240, 30 a week. On hand is 750 less 240, which is 510 units: 360 in stores, because the floor set of 600 has sold 240, and the 150-unit reserve still at the distribution centre, held back because the allocator has not yet released the one core-size refill the plan allows while the option runs behind plan. Eight weeks remain. The option's unit cost is $30, so its margin at the full $80 ticket is $50 a unit.

The pricing analyst compares holding the price with a thirty percent markdown taken in week nine, to a ticket of $56 and a markdown of $24 a unit. The markdown case assumes the rate of sale doubles to 60 units a week, which is the judgement the system cannot make for the analyst and the input the analyst should test against the option's own history and the class's elasticity.

LineHold at $80Mark down to $56 in week 9
Units sold, weeks 9 to 168 × 30 = 2408 × 60 = 480
Units sold by season end240 + 240 = 480240 + 480 = 720
Sell-through at season end480 ÷ 750 = 64%720 ÷ 750 = 96%
Units left against a 75-unit exit target750 − 480 = 270750 − 720 = 30
Revenue, weeks 9 to 16240 × $80 = $19,200480 × $56 = $26,880
Margin, weeks 9 to 16240 × $50 = $12,000480 × $26 = $12,480
Stock left at cost270 × $30 = $8,10030 × $30 = $900
Markdown dollars realised on units sold$0480 × $24 = $11,520

A permanent markdown booked on the 510 units on hand in week nine would be 510 × $24 = $12,240; the example counts the markdown as it is realised on units sold, and Step 1 closes on the same convention.

On these assumptions the markdown recovers more margin in the back half of the season, $12,480 against $12,000, and leaves 30 units to clear instead of 270, which is inside the 75-unit exit the plan set. It counts $11,520 of markdown against the class's planned reductions line, and that is where the financial plan re-enters the decision: of the $90,000 planned, $30,000 has been taken across the class in the first eight weeks, so $60,000 remains, and this one option would use just under a fifth of it. The analyst's question is no longer whether the markdown pays for itself on the option but whether, with eleven other options still to read, the reductions line can afford it, and that is a question only a stack that holds the plan of record can answer at the moment it is asked.

The sensitivity shows why the margin target has to be in the room. If the rate only rises to 45 a week at the lower price, the option sells 360 more units, 600 in total, for revenue of $20,160 and margin of $9,360 in the back half, with 150 units left against the 75-unit target. The markdown then costs $2,640 of margin against holding and still misses the exit, and the right decision may be a deeper markdown, a transfer from the small-door cluster to the doors that are selling, or a hold until the last four weeks. A markdown decided without the plan's margin target is a guess about one option; decided against it, it is a decision about the season. The markdown percent and sell-through rate formulas carry the arithmetic in general form, and end-of-season exit strategies covers the choice between markdown, transfer and hold.

Common failure modes

Merchandising stacks fail in a small number of repeating ways, and each has a mechanism. The list states the mechanism rather than the frequency, because the frequency is not measurable and the mechanism is what a buyer can check for.

  • Buying a suite for one module. A business needs allocation or assortment badly, buys a suite because it covers everything, and goes live on the one member it needed while the others wait for a configuration programme that is never scoped. The result is a point solution at a suite's price, with the seams it bought the suite to close still open. The check is to ask which members will be live at go-live and who configures the rest.
  • Planning in a tool whose hierarchy differs from the ERP's. The planning members run on a hierarchy built for planning, the ERP records transactions on a hierarchy built for finance, and the mapping between them is a table someone maintains. When a class is split in one tree and not the other, the actuals attach to the wrong node, the reforecast is built on mis-attributed sales, and the variance the planner chases is a mapping error. The check is to add a subclass in the evaluation and watch where it appears.
  • Markdown decided without the plan's margin target. The pricing member reads sell-through and weeks of supply and recommends a markdown; the financial plan's reductions line lives in another system, or a file, and nobody reads it at the decision. Each markdown is justified on its own option and the season's margin is missed by the sum of them. The check is the one the worked example makes: ask to see the reductions line against plan at the moment a markdown is taken.
  • Reporting bought before the plan of record exists. A business buys an analytics layer to see what is happening and finds that the plan it wants to compare actuals with is a set of files, so the dashboard reports against a number nobody can change. The mechanism is that reporting is easier to buy than planning and looks like progress.
  • The space plan and the merchandise plan on different calendars. The floor set changes on the visual team's reset calendar and the assortment changes on the planning calendar's deliveries, so options land in stores with no fixture to hold them or fixtures are reset for options that have not arrived. The mechanism is two calendars; the check is whether the reset dates are visible in the assortment's delivery plan.
  • Allocation run from the buy total rather than the grid. The buy is committed at total depth and the split by cluster and channel is decided afterwards by the allocator, so the depth per door is whatever falls out and the presentation minimum is met in some doors and not others. The mechanism is a grid built after the buy; the fix is to build it in the assortment, before the buy, as the worked example does.
  • A point solution with no seam back. A member is bought for its depth and integrated to receive the plan, but nothing it decides flows back: the markdown does not reach the reductions line, the allocation's door-level read does not reach the reforecast, the space plan's capacity does not reach the option count. The stack is connected downhill only, and every uphill change is a person carrying a number.
  • The shadow spreadsheet. The stack cannot carry the vertical's grain or the brand's cluster definition, so the planner re-plans in a workbook beside it, the workbook becomes the plan of record and the system holds a copy. The mechanism is a grain mismatch, and the check is to plan the brand's own object in the evaluation before any other feature is looked at.

Where RetailNorthstar fits

RetailNorthstar's coverage of the planning core is OTB planning, assortment planning, buy planning and allocation, with the product record beneath them. The platform page describes it as a connected commercial workflow system for apparel brands that organizes the full apparel planning cycle, from creative line plan through buying, vendor execution and allocation, into six integrated pillars that share a single data model: Canvas visual line boards, product development, merchandising planning, buying and vendor execution, planning intelligence and a product data foundation. It describes the platform as designed to work alongside a brand's ERP, PLM and data systems rather than replace them, and as live in weeks.

The merchandising planning page describes what it covers of the planning core as OTB planning, assortment planning, buy planning and allocation optimization, connected in a single platform, so that changes to the assortment update the buy plan and changes to the buy plan update the OTB position, with no manual reconciliation between files. It describes apparel-specific capabilities, size curves, seasonal OTB, collection structure and multi-channel buys, as native to the platform, and the platform as designed for mid-market and growing apparel brands that have outgrown spreadsheet-based merchandising planning. The intelligence page describes in-season performance and prior-season hindsight as built into where planning decisions happen, and the product data page describes one product record maintained once and used everywhere. Those pages do not describe a top-down merchandise financial planning module, a replenishment module, a space planning module or a markdown optimization module, so a brand that needs those members of the family should ask how they would attach, as it would of any product covering the planning core.

The criteria in this guide apply to RetailNorthstar as they apply to any product in the category, and a brand should run them against it: one hierarchy, one calendar, one plan of record, the envelope and grid seams tested in the demonstration, and the brand's own vertical grain planned before any other feature is looked at. Which members a brand needs, under which packaging, is the question this guide is meant to help settle before any demonstration, this one included.

Related resources

See how RetailNorthstar connects OTB, assortment, buy planning and allocation on one data model — the planning core of a merchandising stack, between your product record and your transaction record.

Start Free Trial →

No credit card. No commitments.

Common questions

What is retail merchandising software?

Retail merchandising software is the set of systems a retailer or brand's merchandising organisation uses to decide what to sell, how much to buy, at what price, where to place it and when to mark it down. It is a family rather than one product: merchandise financial planning and open-to-buy, assortment planning, item and buy planning, allocation and replenishment, pricing and markdown optimization, space and visual merchandising, product information, and merchandising analytics. Each member owns a layer of the decision at its own grain and cadence, and what makes them one stack is that they read the same merchandise hierarchy, the same calendar and the same plan of record.

What is the difference between retail merchandising software and merchandise planning software?

Merchandise planning software is one member of the family, the planning core. It holds the merchandise financial plan, the open-to-buy, the assortment, the buy, size and pack, allocation and the in-season reforecast, with the markdown calendar it books against the planned reductions line, on one data model, and decides what the business will own. Retail merchandising software is the umbrella above it: the planning core plus the members that sit around it, pricing and markdown optimization, space and visual merchandising, the product record and the reporting layer. A brand can buy the core as one connected system and still have its pricing, its floor, its product data and its reporting in systems that do not read the plan; the umbrella is complete only when every one of those decisions is made against the same plan of record.

What is merchandising management software?

The phrase carries two meanings and a buyer should know which one is in play. In retail systems vocabulary a merchandise management system is the transactional core of a retailer, the item master, purchasing, inventory and price execution, which is an ERP question rather than a planning one. In a buyer's search the phrase also means the software a merchandising leader uses to manage the team's work: one plan of record every role edits at its own layer, a shared planning calendar, reviews run from the same numbers, and decision rights by layer. In practice that is the merchandising planning system used as the team's system of record, with the calendar and review cadence built on it, rather than a separate category of product.

What is software for managing merchandising teams?

It is the merchandising leader's use of the same stack the planners, buyers, allocators and pricing analysts work in. The leader runs four things through it: the planning calendar, with its milestones from hindsight to markdown review; the plan of record, which is the one current approved version of each layer and the history behind it; the reviews, the weekly trade meeting, the open-to-buy review, the line and assortment reviews and the markdown review, each read from the same plan the team edits; and decision rights, which layer each role may change, what needs approval and what is locked. A system that cannot hold versions, approvals and a calendar forces the leader to run the team from a side file, and the side file becomes the plan.

Is retail planning software the same as retail merchandising software?

They overlap but are not the same phrase. Retail planning software usually names the members a retailer's planning department runs, merchandise financial planning, assortment planning and allocation, and in some vendors' usage stretches to store operations planning such as labour scheduling, which is a different discipline. Retail merchandising software is the wider family, which adds pricing and markdown, space and visual merchandising, product information and analytics to the planning members. Store planning software, a third phrase that appears beside both, usually means space and floor planning: fixture layout, planograms and capacity by store.

Should a brand buy a suite, point solutions or a connected platform?

The answer is set by where the reconciliation pain sits, not by revenue. A suite gives several members on one data model from one vendor and trades planning depth and vertical grain for that breadth, with a rollout usually scoped as its own programme. Point solutions assembled one member at a time give the deepest tool for each and leave every seam between them as an integration the buyer owns, with the hierarchy and calendar kept identical in each by hand. A connected planning platform holds the planning core on one data model and attaches pricing, space or analytics where they are needed, trading integration on both sides for connectedness between the planning layers. Spreadsheets give every member at no licence cost and make every seam a person carrying a number. A business whose layers all drift is a platform buyer; one with a single broken member is a point-solution buyer.

What do the members of a merchandising stack have to share?

Seven things, and a stack is one system to the extent that it shares them: the merchandise hierarchy from division to SKU; the calendar, with its retail weeks, seasons, deliveries and reset dates; the product attributes, held as planning dimensions rather than text; the locations, channels, store clusters and grades; the price ladder and price zones; the plan of record, meaning the current approved version of each layer and its history; and the actuals, read once from the transaction record rather than reconciled separately by each member. The test for any pair of systems is to change one of these in one system and see whether the other reads the change or has to be told.

Does the same merchandising software work for footwear, beauty, furniture and other verticals?

The members are the same in every vertical; which ones carry the weight, and at what grain, is not. Footwear's stack is built around the size run, so allocation and replenishment by size within width carry more of the decision than the option count does. Beauty's is built around the shade ladder, the retailer's planogram and reset calendar and continuous replenishment. Home and furniture's is built around long lead times, container minimums, the floor set and dealer prebooks. Toys' is built around the gifting peak and the licensed window, with the markdown exit planned into the buy. A stack that does not carry a vertical's grain natively pushes that vertical's planners back into a spreadsheet beside it, so the evaluation should plan the brand's own object before any other feature is looked at.

RetailNorthstar Editorial Team
RetailNorthstar ·

Share this guide with your team

Copy a link or a pre-written message for Slack, Teams, or email.

// Know where your operation stands

Apply this to your planning operation.

The free Apparel Planning Maturity Assessment benchmarks your operation and tells you exactly which gaps to fix first.

Take the assessment →

Apply these insights with RetailNorthstar.

See how modern apparel brands use RetailNorthstar to put this planning framework into practice.

No credit card. No commitments.

Connected merchandise planning — live in weeks, not quarters.