Promotional calendar
Plan campaigns by brand, category and store; the forecast lifts during the promotion and dips after it.
Promote
Plan the campaign, order the right quantity, measure the effect
A promotional calendar with forecast impact, ABC classification, performance by category and store, and the beauty-specific logic generic tools miss: testers, gifts with purchase, shades and collections.
Plan campaigns by brand, category and store; the forecast lifts during the promotion and dips after it.
See the expected uplift and the cannibalisation on neighbouring references before you order.
A / B / C by revenue, margin or volume, per store, refreshed automatically and used in service-level targets.
Testers are allocated at order validation, tracked separately from sellable stock, and never forgotten on a launch.
GWP campaigns with their own quantities, dates and stores, ordered with the campaign.
Forecast and order at shade level; seasonal collections start and stop cleanly.
Campaigns, launches, holidays and gift-with-purchase operations are planned on one calendar with their dates, scope and expected uplift. The forecast and the proposals integrate them automatically.
Events by brand, category or store
Expected uplift per event
Month, list and timeline views
Every campaign, launch and seasonal event sits on one calendar with its dates, status and the scenario retained. Completed events keep their actual uplift so the next plan starts from facts.
Planned, confirmed, in-progress and completed events
Retained scenario and discount per event
Filter by date range, brand or category
Compare a percentage discount, a bundle or a gift with purchase side by side: predicted lift, revenue, margin, ROI, extra stock to order and the supplier contribution. Select the winner and the forecast adapts.
Predicted lift, revenue, margin and ROI per scenario
Supplier discount and compensation included
One click to retain a scenario and adjust the forecast
Define the trigger (product, brand, category or basket value), the gift and the period. IRISYS estimates the gifts each store needs, tracks stock, allocations and distributions, and flags deficits before the campaign starts.
Trigger by product, brand, category or minimum amount
Gift need estimated per store from the forecast
Stock, allocated, distributed and deficit per store
Testers are tracked separately from sellable stock. Ratios per category, brand or store define how many testers each door needs; zero and low statuses trigger tester orders that are approved in bulk.
One tester per N sellable units, configurable by category, brand or store
Zero, low and adequate status per store and reference
Tester orders generated and approved in bulk
A / B / C thresholds per category on revenue, margin or volume, with the resulting class counts and turnover. Classes drive service-level targets and safety stock.
Thresholds per category
Calculation on last 6 or 12 months
Used in replenishment rules
A promotion or a launch reduces the forecast of the references it replaces. The impacted list can be pasted from Excel and the rate adjusted per launch.
Impacted SKUs per launch
Adjustable cannibalisation rate
Applied to proposals immediately
Expected uplift is planned before the campaign, not discovered on the shelf.
Allocated at order validation and tracked separately from sellable stock.
Each GWP has a campaign, dates, stores and quantities.
ABC per store and per network drives targets and delistings.
Forecast and order at shade level, where the fast and slow sellers really are.
Every campaign is compared to its baseline after the fact.
Per shade
forecast and order granularity
0
testers counted as sellable stock
Per campaign
uplift measured against baseline
Campaigns, testers and GWP are entered in the calendar.
The forecast integrates the uplift and the cannibalisation.
Proposals include the campaign quantities and the testers.
Connected to your ERP
Promotional calendars can be imported by CSV or through the REST API. Campaign quantities, testers and gifts with purchase are ordered on the same purchase orders as regular stock, each with its own line and item code.
Implementation
The same plan on every project. Your team spends a few hours a week; IRISYS does the rest.
ERP connector or CSV / SFTP export. Item master, stock by warehouse, sales history, open purchase orders. Data quality report.
Models trained on 12 to 24 months of history. Accuracy reviewed by category with the planner. Rules set: safety stock, service-level targets, case packs.
IRISYS proposals compared every morning with the current process. Differences explained; rules and events added.
Proposals validated in IRISYS and created in the ERP. Thresholds opened category by category. On-site or remote training.
Yes, by CSV or through the REST API, or planners enter it in IRISYS.
Testers are ordered as separate lines with their own item code or flag, depending on how your ERP manages them.
Both. Network ABC drives assortment decisions; store ABC drives service-level targets.
From similar past campaigns on the same category and store when they exist, otherwise from the uplift entered by the brand manager, then measured after the fact.
Yes. Testers are their own items with their own cost price in the ERP; IRISYS reports tester consumption and value per store and per launch.
Bring your promotional calendar to the demo. We show the uplift IRISYS would forecast and the testers it would allocate.