Data engineering

Three feeds, one record

We reconcile the inventory feeds behind your forecasting pilot, give each feed a named owner and measure its quality every week.

Request an assessment See the Hollis case

From three IDs to one trusted SKU

We match identifiers across your feeds, settle every conflict with its owner and log each change so the next sample can be trusted.

Match every identifier to one SKU

We take the same 500 sampled records from each feed and match their SKU identifiers: exact matches first, then documented rules.

  • Exact matches confirmed across all three feeds
  • Every match rule written down and owner reviewed
  • Unmatched records listed, never guessed

One of three assessment deliverables

Every feed gets a named owner

The feed ownership register lists each feed, who answers for it, how often it refreshes and which checks run on it.

Feed ownership registerHollis Supply · version 3 · sample
  • 6 feeds
  • 5 signed off
  • 1 without owner
Feed System Owner Refresh Checks Status
Stock on hand WMSThree sites DWDana WhitlockWarehouse operations every 15 min ID matchFreshness Signed off
Item master ERPItem tables MOMarcus OkaforDemand planning nightly 01:00 SchemaCompleteness Signed off
Open purchase orders ERPPurchasing PRPriya RamanPurchasing hourly Completeness Signed off
Supplier catalogue EDI 83214 suppliers PRPriya RamanPurchasing daily 02:00 ID matchLate file Signed off
Advance shipping notices EDI 856Inbound Owner: unassignedProposed: receiving per shipment ID matchLate file Blocks sign-off
Stock transfers WMSSite to site THTomás HerreraInventory control every 30 min Conflict rate Signed off

Sample register. Feeds, systems and owners are fictional; your register is built from your own feeds during the assessment.

Data quality you can watch weekly

Five measures run on every feed and land on one page, so an owner sees a problem before the forecast does.

Freshness

How old each feed is right now, against the limit its owner agreed.

8%

40 of 500 records with a missing or conflicting SKU identifier

Conflict rate

Measured at the assessment, re-sampled every week. The pilot waits for 1% or below.

Completeness

Required fields filled in the item master, field by field.

Schema drift

A renamed column is caught before it breaks a match rule.

Late files

Each nightly supplier file, timed against the cutoff the forecast needs.

Repairs run on a weekly loop

Each week the same feeds are re-sampled, owners sign off their fixes and the issue rate is checked against the 1% gate.

  1. Monday

    Re-sample

    500 records from the same three feeds, drawn the same way as at the assessment.

  2. Tuesday to Thursday

    Repair

    Fixes from the repair plan in priority order, each one written to the change log.

  3. Thursday

    Owner sign-off

    Each feed owner reviews and approves the changes made to their own feed.

  4. Friday

    Gate check

    The sampled issue rate is compared with the gate your operations owner agreed.

    ≤1% The pilot can start

Above 1% the loop runs again next Monday

Start with a two-week assessment

€6,000, fixed before it starts. A readiness report, a feed ownership register and a repair plan your owner can act on.

Request an assessment See the Hollis case