Local vs General Assortments in SAP IS-Retail – Key Differences and Business Use Cases
Over this comparison article, which explains the two main assortment types within the SAP IS-Retail system, you learn when to use local versus general assortments and the business risks.
Key Takeaways:
- General assortments define the company-wide core selection of articles and are created at chain, region, or category-management level during assortment planning for consistent availability across many stores.
- Local assortments tailor the assortment for a single store or a small cluster, allowing store-level additions, removals, and exceptions to reflect local demand, space constraints, or legal requirements.
- Assortment assignment uses the assortment hierarchy: general assortments are assigned at higher organizational levels and inherited by lower levels, while local assortments override or supplement that inheritance at the store level.
- Typical business use cases: general assortments for core SKUs, national promotions, and standardized replenishment; local assortments for regional specialties, seasonals, test assortments, and stores with limited shelf space.
- Operational trade-offs: general assortments reduce master-data complexity and simplify forecasting and replenishment; local assortments increase maintenance and versioning effort but improve local sales relevance and customer fit.
Structural Comparison of Assortment Types
Structural comparison helps you see Local Assortments map 1:1 to sites while General Assortments group SKUs across stores in SAP IS-Retail. A detailed analysis of the two main assortment types and their foundational roles in retail data management. Recognizing you should consult the SAP Retail Assortment Setup Guide | PDF for configuration nuances.
| Scope | Local: site-specific · General: cross-store |
| Relationship | Local: 1:1 site mapping · General: grouped catalog |
| Flexibility | Local: high per-site variance · General: standardized |
| Maintenance | Local: decentralized edits · General: centralized updates |
| Use Case | Local: site promotions/assortment · General: chain planning |
- Local Assortments – site-tailored SKU lists
- General Assortments – centralized SKU groups
- SAP IS-Retail – supports both models for master data
General Assortment Attributes and Flexibility
General setups let you apply General Assortments for cross-store planning, centralized attribute control, and bulk replication so you can reduce repetitive edits while relying on master data governance and versioned catalogs.
Local Assortment 1:1 Site Relationships
Local configurations let you set inventory, promotions, and category mixes per site via Local Assortments, providing targeted merchandising and sharper store-level responsiveness without impacting chain-wide catalogs.
You manage Local Assortments knowing they create precise store assortments, increase maintenance overhead, and raise the risk of data inconsistency if governance is weak; you gain site-specific optimization for traffic, seasonal demand, and local promotion execution.
Operational Logic: Creation and Assignment
Local assortments are created per store during monthly or seasonal planning runs, often by copying a centrally maintained general assortment from the Assortment Catalog; general assortments are created centrally during planning cycles. You assign them via manual store assignment, mass assignment (CSV/IDoc), or by mapping assortment profiles to store and DC hierarchies.
System Triggers for Assortment Generation
Systems create general assortments at defined planning-cycle start dates or when assortment validity ranges are set, while local assortments are triggered by SKU master-data changes, new-store opens, or when you execute the background assortment-generation job. You can schedule these jobs or run generation ad hoc to control timing.
Assignment Procedures for Stores and Distribution Centers
Assignment uses mapping of assortment IDs to store IDs or DC IDs through assortment profiles, manual links in the Assortment Catalog, or bulk imports; you can enable inheritance from store hierarchies so general assortments propagate to child stores and allow local overrides at the store level.
When you assign, use three methods: manual edits in the Assortment Catalog for single-site changes; mass assignment via CSV/IDoc or BAPI for bulk propagation; and profile-based mapping that binds assortments to distribution centers or assortment groups. You must protect local edits with validity dates and audit logs because mass jobs can overwrite local overrides.
Strategic Deployment Across Retail Formats
You adapt assortment strategy by format; this is an exploration of how different retail formats use assortment strategy to control product availability and inventory flow, letting you align stock profiles, replenishment windows, and delivery frequency to each store type.
Standardized Assortment Strategies for Large Formats
Large-format stores standardize assortments across regions so you maintain consistent product availability; centralized replenishment, wide SKU ranges, and uniform planograms stabilize inventory flow and reduce local stockouts.
Site-Specific Range Control for Specialized Retailers
Specialized retailers limit SKUs per site so you tailor assortments to local demand, using tight range control and faster replenishment to protect product availability and optimize inventory flow.
Tailored site-specific range control lets you use POS-driven forecasts, weekly sales, and seasonal triggers to set shelf-by-shelf ranges, adjust safety stock, and define shorter replenishment cycles. You employ vendor-managed replenishment, store-cluster segmentation, and exception alerts for slow movers; this exploration of how different retail formats use assortment strategy to control product availability and inventory flow reduces overstocks, lowers markdown risk, and protects margin.
To wrap up
As a reminder you use Local assortments in SAP IS-Retail for store-level product mixes and short promotions, and General assortments for company-wide master assortments and standardized rollouts, supporting consistent SKU planning across stores; consult IS-Retail Assortment for implementation details.
FAQ
Q: What are Local and General Assortments in SAP IS-Retail and how do they differ?
A: General assortments are centrally defined sets of products intended for a chain, region, or business unit and represent the master selection used for merchandising and planning. Local assortments are store- or site-specific selections derived from a general assortment or created independently to reflect local demand, space, or legal requirements. General assortments control the core assortment shared across multiple locations while local assortments control final on-shelf availability and permit substitutions, deletions, or additions for a specific store. System-wise, general assortments are maintained at higher organizational levels (for example, sales organization/division) and local assortments are maintained at plant or store level, with replication or assignment processes to push central selections down to stores.
Q: When should a General Assortment be created versus a Local Assortment?
A: Create a general assortment when a product selection must be standardized across many stores to support centralized procurement, promotions, pricing consistency, and category strategies. Create a local assortment when a store needs customization for limited shelf space, regional tastes, seasonal events, legal restrictions, or franchise-specific rules. Use a general assortment as the baseline for planning, forecasting, and supplier negotiations; use local assortments to adapt that baseline to store realities, drive space optimization, and prevent stockouts or overstocks at the local level.
Q: How are assortments assigned and which one takes precedence in SAP IS-Retail?
A: Assortments are assigned via master-data links that connect assortments to sales organizations, distribution channels, stores (plants), or assortment groups. A general assortment is typically assigned to a higher organizational node and propagated to child nodes; a local assortment is assigned directly to the plant/store. Local assortment definitions override or refine the propagated general assortment for that store when the system resolves availability and planogram content. Assignment processes include copying a general assortment into a local data object for editing, direct assignment of a general assortment to multiple stores, and scheduling replication jobs to distribute changes to point-of-sale or store systems.
Q: How do different retail formats use general and local assortments to control product availability?
A: Convenience stores focus heavily on local assortments because small footprint and immediate demand patterns require tight local control over SKU counts, pack sizes, and quick-turn items. Supermarkets use a hybrid approach: central general assortments for staple categories and local assortments for fresh produce, regional brands, and promotional layouts. Hypermarkets and big-box formats rely on broad general assortments to ensure wide selection and procurement efficiency while allowing local assortments in peripheral categories or seasonal zones. Franchise and licensed-store models implement a mandated general core assortment plus optional local assortments that franchisees can select from, enforcing compliance for key SKUs while permitting market adaptation.
Q: What operational considerations and business use cases should merchandising, supply chain, and store teams plan for when using local and general assortments?
A: Define governance and change-control for who may create, change, or approve general versus local assortments to prevent SKU proliferation and conflicting directives. Use general assortments for centralized forecasting, category management, supplier contracts, and promotions that require consistent execution. Use local assortments for space planning, planogram adjustments, local promotions, and short-term seasonal or event-driven selections. Ensure integration between assortment master data and replenishment/ordering: local assortment changes must reflect in ordering logic and distribution allocation to avoid supply gaps. Implement reporting that compares general targets against local performance for SKU rationalization and to identify opportunities to roll local winners into the general assortment.