One system runs the US operation for a non-alcoholic brand.
AvenorOS holds inventory, orders, retail EDI, field sales, trade spend, marketplace results and the monthly P&L for the US operation we run for you. You get one login. Behind it sits the team that does the work.
- Revenue, month over month
- $248k
- ↑ 23% vs prior period
- Fulfillment rate
- 98%
- on-time · 99.2% target
- Active orders
- 1,847
- ↑ 14% week over week
- Retail doors
- 312
- ↑ 38 new this month
Nine tools a brand buys to run the US, and what falls between them.
A European brand running the US on its own assembles these. Each one holds a piece. The work between them is done by hand, in spreadsheets, every week.
Cases on hand at one warehouse, by SKU.
Lots, best-before dates and inbound containers live elsewhere. Nobody sees stock in transit against orders already taken.
Inventory by SKU, lot, location and best-before, with inbound shipments counted before they land.
Orders from one storefront, pushed to the warehouse.
Amazon, Faire and distributor orders arrive by other routes. Allocation across channels is a judgement made in a spreadsheet.
One order queue across Shopify, Amazon, Faire, Airgoods and distributors, allocated from one inventory pool.
Purchase orders, shipping notices and invoices in the format a chain requires.
Chargebacks arrive weeks later on a separate statement. Matching them to the order that caused them is manual.
Retail purchase orders, shipments, invoices and the chargebacks against them on one record.
Contacts and a pipeline, built for a team selling software.
It does not know a door, a depletion or a reorder. Velocity per account is entered by hand or never.
Accounts by focus city with depletions, placements and reorders per door.
Visits, samples and orders written up from the road.
The visit log and the distributor depletion report never meet. A rep’s week and a door’s velocity are reconciled at month end.
Visit log, sample log and distributor depletions on the same account record.
Promotions and allowances agreed with a distributor or a chain.
The deduction that pays for the promotion lands in receivables with no reference to it. Finance guesses.
Every promotion carries its budget, its window and the chargebacks matched to it.
Amazon and Shopify each report their own sales, fees and ad spend.
Neither knows the other’s price, stock or promotion. Sell-through across DTC, Amazon and retail is assembled by hand.
Sell-through by channel on one page, with the DTC, Amazon and wholesale price of each SKU beside it.
Freight, duty and broker fees averaged across a shipment.
Cost per unit drifts with each container and each exchange rate. Margin by channel is recalculated when someone has time.
Landed cost per SKU per lot, and contribution margin by channel computed from it.
Exports from each tool, pasted into one deck every Monday.
The deck is out of date by Tuesday. A question about a number goes back to whichever tool it came from.
Weekly KPIs and a monthly P&L built from the records above, with the variance written by the person who ran the month.
Six facts a generic tool has to be taught.
A generic operations system starts empty and learns beverage one workaround at a time. AvenorOS starts with these.
- 01
A case is 12 bottles of 750 ml glass and ships at close to 15 kilograms. A generic system counts units; the parcel rate, the pallet count and the breakage allowance all follow from the case.
- 02
A state has its own rule for what 0.0% may be called and where it may be sold. The ship-to address decides the label term and the channel. A generic order tool sees a ZIP code.
- 03
A distributor deducts the cost of a promotion from a later invoice. The deduction is matched to the promotion that caused it, or it becomes a dispute. A generic ledger records a short payment.
- 04
One SKU carries a DTC price, an Amazon price and a wholesale price, and a policy about how far apart they may sit. A generic catalogue holds one price.
- 05
Best-before dates follow the lot. Stock is rotated by date and pulled before it is unsaleable. A generic warehouse count has no date.
- 06
Every shipment from a European supplier needs verification records under FSVP. The record belongs on the shipment. A generic system files it in a folder.
Visibility into a team doing the work.
AvenorOS reports on an operation we run. You read the system. Our team fills it as the work happens: the container is booked, the purchase order ships, the door is visited, the deduction is matched. Four things reach you on a fixed cadence.
- Weekly KPIs every Monday: revenue, spend, pipeline and the priorities for the week, each with an owner.
- A monthly P&L with the variance written by the person who ran the month.
- Milestones with go/no-go criteria set before the phase starts.
- A shared Slack channel with same-day answers from a principal.
Five roles, each with its own page.
A founder, a marketer, a finance lead, an operations lead and a field-sales lead each open a different screen first.
- AvenorOS for foundersWeekly KPIs, the monthly P&L and the milestone calls.Read the guide
- AvenorOS for marketingSell-through by channel and the promotion that moved it.Read the guide
- AvenorOS for financeLanded cost by lot, margin by channel, deductions matched.Read the guide
- AvenorOS for operationsStock, orders and paperwork on one set of records.Read the guide
- AvenorOS for field salesEvery door, its depletions and its last visit.Read the guide
Walk through AvenorOS with us.
We open the system on your current setup, show what each of your team would see, and lay out the rollout.