Propel Foods

Enter the password to view this page

Propel Foods process mapping

Input vs Output: Where The Same Information Is Re-Entered

One-page view from both sessions to help the team align on duplication hotspots before choosing tooling.

Session 1 (Outputs): Suzanne, Jen, Roxanne, Sherrie Session 2 (Inputs): Sherrie + Jen shared one mic Sources: transcript + whiteboard OCR for each session

Highest Duplication Hotspots

Filter by category. Red items are the biggest duplicate-entry pain.

1) Listing info is re-entered in many formats

Brand spec details start in the Listing and Promotional Planner, then are re-keyed into retailer-specific listing forms, distributor templates, and sometimes portals.

Signals from sessions: each retailer format differs even when fields are same; some portals require direct entry.

2) Promo calendars and deal sheets duplicate by channel

The same offer data is maintained in Excel planners and then re-submitted through portal or partner templates (ex: Sobeys CMAP variants, Loblaws portal, UNFI sheet, Purity portal).

Team callout in session: "It is a lot of duplication of work - a ton."

3) Reporting is pulled repeatedly from the same base data

Gap, opportunity, and new distribution outputs use overlapping Qlik data, but are rebuilt in separate Excel templates by different people.

Example from session: opportunity process compares many Qlik pulls in Excel; CAMs run similar gap pulls independently.

4) Forecasting exists at multiple levels that do not always align

Brand-level forecast and CAM account-level forecast are both manual-heavy and sit in separate files/workflows, then feed more outputs.

Session notes: alignment gap between brand and sales forecast logic.

5) Business updates are unstructured and repeated

Important updates move through email, Teams calls, monthly summaries, and ad hoc notes. Same message appears in multiple places with no single structured field.

Examples given: planogram timing, listing status, launch updates.

6) Contract terms are copied into downstream sheets

Contract starts as legal doc (Word/PDF signed), then key terms are re-entered into master sales, commission logic, Qlik rules, and budget/reporting workflows.

Low frequency vs promo/reporting, but high impact if entered wrong.

Same Data, Multiple Entry Points

Plain-language matrix of where duplication is happening now.

Information block Primary source Where it gets re-entered Teams touched Dup risk
Item specs + listing attributes Brand inputs into Listing and Promotional Planner (plus PDF/email/portal inbound) Retailer listing forms, distributor setup forms, portal entry screens BDM, Sales, Trade, Data High
Promotions and deal mechanics Planner tabs (calendar, case stack, brand guidelines) Deal sheets, account-specific templates, retailer/distributor portals BDM, Sales, Trade High
Gap, opportunity, new distribution Qlik data + portal data Separate Excel outputs by team and audience Sales, BDM, Data High
Forecast values Springboard -> Qlik + manual planning files Account forecast files, brand forecast files, retailer listing/promo asks Sales, BDM, Trade, Data Medium
Business status updates Calls, meetings, email, ad hoc messages Monthly reports, direct emails, team chat context All client-facing teams Medium
Contract rules (rate, territory, exclusions) Legal contract documents Master sales sheet, commission reporting, budgeting, Qlik rule handling BDM, AR/AP, Data Low

Duplication By External Path

Where re-entry tends to happen as data moves outward.

Brands -> Internal

  1. Brand sends mixed formats (Excel/PDF/email/portal exports).
  2. Team standardizes into planner/template.
  3. Same values are then copied to reports, forecasts, and planning files.

Internal -> Retailers

  1. Planner data mapped to retailer-specific listing and promo forms.
  2. Same deal information entered again in portals for approvals.
  3. Performance reports combine Qlik plus portal-only data in separate files.

Internal -> Distributors

  1. New vendor/item setup repeats listing and contract details.
  2. Offers sent through distributor-specific template or portal.
  3. Forecast/insight updates are rebuilt from overlapping data.
Open detailed full map