A fashion ERP needs a different base unit than a generic one
Accounting software treats a product as a SKU with a quantity. A fashion business sells a size run across colors, and the number that actually matters is the count per size, per color, per store — that is the unit Sacs is built around, not an add-on to a flat catalog.
The season, covered from receiving to markdown
Every item below is a shipped feature, not a roadmap promise.
The size-and-color grid is the base unit
A generic ERP treats a product as one SKU with a quantity. A style isn't one SKU — it's a size run across colors, and the count that matters is per size, per color, per store. Sacs builds inventory around that grid from the start, not as a workaround bolted onto a flat product table.
Distribution from your warehouse (CEDIS)
The first shipment of the season gets allocated to each store from your distribution center, with receiving done by scanning cases in — not a spreadsheet reconciled after the fact.
Sell-through, ABC and rotation, by store
How each style is moving by week of life, what is about to sell out, and what is turning into markdown stock — read weekly across every location, not once a season.
AI-assisted stock leveling
A size that isn't moving in one store and is running out in another gets proposed as a transfer by the system; your team approves it. This is on the Automate plan — it's live today, not on a roadmap.
Wholesale and retail on one catalog
Retail, mid-wholesale and wholesale price lists on the same inventory — one style, one stock count, different prices by customer type and order quantity.
Ecommerce and social channels on the same stock
Online store, Facebook, Instagram and TikTok Shop pull from the same inventory as your physical stores. Nothing gets re-published or re-counted per channel.