Price Optimization on Epicor, for merchandising
Price on elasticity you can measure. Ward runs it off Epicor, scoped to what a VP Merchandising owns.
Price Optimization on Epicor, for merchandising
Your category managers are drowning in spreadsheets. Ward raises the signals that change a merchandising decision.
Here is price optimization in plain terms. Ward monitors price elasticity shifts in real time and recommends adjustments that protect margin without sacrificing volume.
How it runs. Ward continuously measures price elasticity by category, tracks competitive pricing signals, and models the margin-volume tradeoff.
The connection itself. Ward connects via Epicor REST API. Compatible with Epicor Prophet 21 and Epicor Eclipse.
What you get
- Category-level price sensitivity
- Competitive price monitoring
- Margin-volume tradeoff modeling
- Real-time elasticity measurement
Chat
Ask anything. Ward routes to the right agent and returns cited answers.
I pulled Store 37’s last 28 days against the chain baseline. Two root causes, both compounding.
| Signal | Finding |
|---|---|
labor_efficiency | Rev/labor-hour −22% vs. cluster, staffing mismatch at 11a–1p peak |
inventory.fresh | Fresh fill 83%, backroom replenishment lag at 2–4p |
promo.lift | BOGO crackers cannibalized Brand Y by 28%, net category +6% |
Recommend: re-baseline Store 37 schedule against true peak, raise replen window to 1p, and review the BOGO before next cycle.
labor_scheduling…
Reporting
Pinned views built from saved data-lake queries. Every number re-derivable from its SQL.
| Model | Horizon | MAPE |
|---|---|---|
holt_winters | 4wk | 4.1% |
arima_sarimax | 13wk | 8.9% |
gbm_demand | 1wk | 2.1% |
bayes_hier | new store | 11.4% |
Sources
Connect external systems to the data lake.
| Name | Type | Last sync |
|---|---|---|
sap_pos_transactions | import | 2m ago |
sap_inventory_shrinkage | import | 2m ago |
sap_labor_scheduling | import | 14m ago |
retail_inventory_weekly | import | 1h ago |
retail_google_ads_daily | import | 1h ago |
retail_meta_ads_daily | import | 1h ago |
retail_ga4_website_daily | import | 1h ago |
Policies
Browse and manage Cedar access policies for your tenant.
| Policy ID | Effect | Resources |
|---|---|---|
merch-read-default | permit | Model::* |
finance-read-shrinkage | permit | Model::"inventory_shrinkage" |
vendor-blocked | forbid | Model::"labor_*" |
region-west-only | permit | Tenant::"acme" |
Why this combination
is its own problem.
Price Optimization needs sales orders and inventory at minimum. Epicor carries both, at the grain the model needs. That is the whole integration story: no middleware, no staging warehouse, no custom extract.
What Ward has eyes on.
Price on elasticity you can measure. Ward runs the model continuously rather than on a reporting cycle, which is why a finding lands the morning the pattern starts instead of at the end of the period.
The connection to Epicor is read-only and runs on your schedule. Ward reads straight from sales orders, inventory, and the rest of the feed, then cross-references it with external context your ERP does not carry: weather, local events, competitor pricing.
What the first 90 days
actually look like.
-
01
Week 1: connect
Read-only credentials to Epicor. Ward ingests sales orders, inventory, purchase orders and starts building baselines. First cards land inside 48 hours, before baselines are stable, so you can see the shape of the output early.
-
02
Weeks 2 to 3: baselines
Ward needs roughly two weeks of history per store to separate a real deviation from normal variance. During this window the cards are directionally right and the thresholds are still moving.
-
03
Weeks 4 to 12: steady state
Ward hands you insight cards every morning, each with the cause and what to do about it. Volume settles at a level a single person can read over coffee. The measure of success is not how many insight cards arrive, it is how many get acted on.
How Ward connects to Epicor
Ward integrates with Epicor for home improvement, furniture, and building supply retailers. Inventory, purchasing, production, and sales data power insight cards.
Setup: Ward connects via Epicor REST API. Compatible with Epicor Prophet 21 and Epicor Eclipse.
Data Ward reads from Epicor
Impact metrics with Epicor
Data lake enrichment
Ward enriches Epicor data with: Sales orders, Weather & events, Contractor/Pro data, Competitor pricing, Vendor scorecards
Your category managers are drowning in spreadsheets.
- ×Promo planning still runs off last year's playbook
- ×Assortment reviews happen quarterly when they should happen daily
- ×Price changes chase the market a week behind it
- ×No visibility into true cannibalization across categories
- ×Vendor negotiations lack real-time sell-through evidence
- ✓Insight cards flag promo cannibalization the day it happens
- ✓Assortment gaps and whitespace opportunities surface automatically
- ✓Price elasticity shifts detected before margin erosion compounds
- ✓Category-level performance cards replace manual spreadsheet reviews
- ✓Vendor scorecards generated from actual fill rate and quality data
Retailers lose an estimated $300B+ annually to suboptimal assortment and promotional decisions. Source: McKinsey & Company
Frequently asked questions
Ward connects via Epicor REST API. Compatible with Epicor Prophet 21 and Epicor Eclipse. Data points include: Sales orders, Inventory, Purchase orders, Customer accounts, Pricing tiers, Vendor performance.
Your category managers are drowning in spreadsheets. Ward solves this with automated insight cards: Insight cards flag promo cannibalization the day it happens. Assortment gaps and whitespace opportunities surface automatically. Price elasticity shifts detected before margin erosion compounds.
First insight cards arrive within 48 hours of data connection. Ward needs approximately 2 weeks to establish stable baselines for your specific operation.
No. Ward sits on top of your existing stack. It is the proactive intelligence layer that watches your data continuously and delivers insight cards, so your team acts on findings instead of hunting for them.
Related solutions
See what pricing problems Ward catches.
Root causes, not just alerts. See it on your data.
Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly
Find out what your data has been hiding.
Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.