1. Supply Chain Analytics
  2. Features
  3. Service Snapshots
Feature · Service Snapshots

Service Snapshots

Prepare fill rate snapshots by scope and date and lock them after independent approval.

OverviewService Snapshots Awaiting Lock
Supply Chain Analytics · Service Snapshots

Service Snapshots Awaiting Lock

Approval waits for the procurement approver

New
Scope nameAs of dateRequested unitsFilled unitsParentRevision
Scope 44227 Oct840290PR-72199610
Scope 11618 Oct70720PR-4369830
Scope 66225 Oct70250PR-36245880
Scope 88406 Oct400530PR-36417360
Scope 46827 Oct210280PR-56159160
6 of 6 records
Scope 442Service snapshots · SS-76913
As of date27 Oct
Requested units840
Filled units290
ParentPR-72199
Revision610
Example screen with sample data

What you can do

Fix the fill rate you report

Fill rate changes as late deliveries arrive. A service snapshot fixes it for a scope and date: the scope name, such as a supplier, category or region, the as-of date, the requested units and the filled units. Each snapshot is linked to a purchase request and an organization.

Before a snapshot can be locked, it is checked: the scope must be set, the as-of date cannot be in the future, requested units must be above zero and filled units must be between zero and requested. Its version is frozen when submitted, and it is completed only after an independent approval. Rejected snapshots stay on record.

How the work is organized

  • Scope and date. Each snapshot answers one question: how much of what was requested was filled, for this scope, as of this date.
  • Checks before lock. Impossible figures are refused before approval.
  • Locked after approval. A completed snapshot is the figure you report.

What to agree during setup

Agree the scopes you report on and how often: weekly by supplier, monthly by category. Decide what counts as filled. Agree who prepares and who approves snapshots, and how a correction to a locked period is handled.

Check the handoff on an actual case

At the end of May, the analyst prepares a snapshot for the beverage supplier scope as of 31 May: 9,600 units requested and 9,120 filled, a 95 percent fill rate. The snapshot is submitted and its version frozen. The approver checks the units against the accepted lines and approves it, and it is completed with the decision date.

The supplier later argues that 200 units arrived on 1 June. Because the snapshot is locked as of 31 May, the reported May fill rate stays at 95 percent, and the late units show in June.

During the pilot, prepare snapshots for two scopes and one week, including one with filled units above requested. Confirm the impossible one is refused, the others lock after approval and the locked figures match the accepted lines.

What your team sees

  • Service Snapshots Awaiting Lock — Submitted snapshots waiting for approval.
  • Service Snapshot Register — Every snapshot by status with scope and units.

Follow the work through

Check approver access before go-live.

What it keeps track of

Data model
Service snapshots
Reconciled service snapshot records supporting the lock operation.
Purchase requests
Purchase demand records with lifecycle, owner, counterparty and approved commitment.
Organizations
Operating organizations that own supply chain records.

Who uses it

Permissions
Supply Chain Analyst
, Procurement Approver.
The analyst prepares snapshots.
The approver locks them.

Set up Supply Chain Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started