OZP

000%

OZP Studios
CommerceOperationsPlatformCompleted

AXORA-3

Orders arrived as texts, emails, and voicemails. Inventory was a guess until the truck left.

Client
Regional food distributionWithheld by agreement
Year
2024
Role
Product, design & engineering
Type
Commerce
Approach
Catalog · Ordering · Inventory
Screenshot
01

Where it started

A regional distributor. Restaurants ordered by texting a rep who had been there fifteen years. The catalog was a PDF. Inventory was whatever the warehouse said that morning, which was often wrong by lunch.

What was hard

The catalog had customer-specific pricing, cuts, and substitutions. A public storefront would have been a lie. Reps still needed to exist. The system had to take the order without pretending the relationship was not the product.

Screenshot
02

What we built

A logged-in catalog. Price lists per account. Standing orders. Substitutions the warehouse can actually fill. Reps see the same cart the kitchen sees. Inventory from the warehouse system, not from a sheet.

What changed

Most orders do not start in a text thread. The PDF catalog is an export. Reps still call. They do not retype.

Scope

  • Account-priced wholesale catalog
  • Standing orders and substitutions
  • Inventory from the warehouse system
  • Rep view of the same cart
  • Order history and reorder

Next

Ready to take the next step?

Work with a small team that moves with intent. Clear communication, strong execution, and builds that feel inevitable once they exist.

Start a project