Cartology: Rep app workflow for in-store POS campaigns

From email chains to in-store visibility.

We designed a proposed digital workflow that brings Cartology's in-store POS campaigns into Compass, the Woolworths field rep app, so campaign briefs become store tasks and every scanned action feeds Cartology's Google Cloud Platform every 30 minutes.

Retail / Grocery
Software development
Data engineering
Project

31ranked requirements

30 minaction feed to Cartology GCP

~100vendors on Empower

~10 wksrequirements to mock-ups

The Challenge

What stood in the way.

Every week new POS campaigns went into Woolworths stores and expired ones came out, coordinated by email across five parties. Briefs went to agencies by email, reps logged actions in each agency's own system

Hand-built allocation table

The weekly allocation table was stitched together by hand from four sources: Salesforce bookings, SAP Webi product ranging

Ranging chased by email

Missing ranging lists delayed the build, and copying last week's sheet let jobs move between weeks and made data easy to get wrong.

Unactionable failure codes

One-line codes such as "PROD NOT RANGED" gave no way to tell whether to reprint, re-range or escalate.

Results in every format

Each agency returned results in its own format, so buying support reshaped every file before Cartology could use it.

Our Solution

How we answered it.

The proposed design reuses Compass's existing task-list framework: the brief becomes tasks, reps act by scanning, and every action flows to Cartology's Google Cloud Platform. Campaign dates decide the task

ProblemFive parties coordinated every hand-off by email.
Our answerThe design replaces each email hand-off with Compass: the brief is uploaded once and shown as store tasks, and results flow straight to Cartology's GCP.
ProblemAgencies captured and reported data in different ways.
Our answerCartology fixed one data standard for briefs and results before the app was built, so every agency reports the same fields against the same WOW code.
ProblemOne client could hold many vendor numbers, complicating permissions.
Our answerVendors are identified by SSG and PartnerHub numbers, and an admin approves every vendor.
ProblemWeighed and random-weight items are hard to scan reliably.
Our answerWoolworths supplies a unit-of-measure mapping so these items resolve correctly.

How It Works

The parts that made the difference.

One field data standard

Before any build, Cartology fixed one brief and results format for all agencies, keyed on the Booking Number (WOW code) printed on every artwork so barcodes can replace images.

Store task lists

Install, audit and removal tasks appear with dates and in-store location, in Installation and Audit tabs beside the usual availability alerts.

Scan-to-confirm installation

Reps answer yes, take a photo and scan the barcode. If they cannot install, they pick a reason, and the scan button appears only when the reason needs it.

Actionable exception reasons

Non-installation reasons were rebuilt with follow-up questions, photos, named store contacts and comments, so Cartology can see what to fix.

Results

What changed for the client.

The design turns campaign execution into one data loop: brief in, scanned actions out, results in Cartology's GCP on a 30-minute feed. These are design objectives: the project records do not quantify post-rollout performance.

Briefs uploaded once and shown as tasks, instead of emailed to each agency
Rep actions captured by barcode scan in Compass, rather than in each agency's own system
Results fed to Cartology's GCP every 30 minutes, replacing emailed files reshaped by hand
Items identified by the WOW code on the artwork instead of by artwork images
Failure reasons with follow-up questions, store contacts and photos in place of one-line codes
Audits completed in one multi-scan with expiry alerts