Operations software for food & beverage manufacturers

Run the whole plant
from one record.

Orders, production, purchasing, receiving, inventory, costing and traceability in one connected system. A customer order becomes your production plan, your buy list, your lot code and your paperwork — without anybody typing it twice.

Built on the floor

Written inside a working Texas food manufacturing facility.
Our first customer was ourselves.

What it runs

An inventory system tells you what you have. That’s the easy half.

SupplyProLog tells you what to make this week, what to buy to make it, what it cost when it’s done and where every case went — twelve parts of the operation, connected, so the work done in one is already done in the rest. Two of them are inventory.

Every one of these is live in the product today — nothing here is a roadmap

Operations dashboard showing four open orders worth $33,959, twenty-one active SKUs and a list of recent customer orders by status.
Monday morning, whole plant

The information isn’t missing. It’s scattered.

You have the orders. You have the recipes. You know what came in the door last Tuesday and roughly what’s on the racks. Every number a manufacturer needs already exists somewhere in the building — in a spreadsheet, an inbox, a clipboard by the kettle, and one person’s head.

None of those places talk to each other. So the same information gets typed in three times, and every question anybody asks costs an hour to answer. It isn’t a software problem — it’s an hours problem, and it only gets louder as you grow. SupplyProLog gives those hours back by connecting work you already do.

One record in.
Every document out.

Follow a single week of orders down the line. Every panel below is produced by the entry before it — nobody re-keys anything, and nothing is assembled on a Friday afternoon.

Purchase ordersSalsa Verde 16oz · Entered once
Order · customerJarsDue
PO 26534  Lone Star Grill Group48012 AUG
PO 11121  Mesa Market Foods57612 AUG
PO 080526  Bodega Norte24013 AUG
ONE PRODUCT, ONE WEEK1,296ONE RUN

Three brands want the same jar in the same week. Keyed in once, they stop being three problems and become one production run.

Bill of materialsWhat 1,296 jars consumes
MaterialFor this run
Tomatillo690 LB
Green Jalapeño205 LB
Peeled Garlic34 LB
Apple Cider Vinegar96 LB
Kosher Sea Salt22 LB
+ 4 MORE — PACKAGING, SPICE, LABELS9 IN ALL

The recipe already knows what a batch takes. Multiply it by the run and you have the shopping list — without anybody opening a spreadsheet.

Against inventoryOn hand as of this morning’s dock scans
2materials won’t cover the runThe other 7 are already on the racks
ShortNeededOn handGap
Green Jalapeño205 LB138 LB67 LB
16oz Squat Jar1,296 EA860 EA436 EA

On hand is whatever was scanned in at the dock and eaten by the last batch — not a number somebody counted a fortnight ago.

What to buyThe gap — not a monthly guess
Delta Produce SupplyGreen Jalapeño70 LB  ·  $63.002-day lead · cut 06 AUG
Gulf Coast Jar16oz Squat Jar480 EA  ·  $206.404-day lead · cut 06 AUG
TWO PURCHASE ORDERS RAISED AGAINST THE RUNTOTAL$269.40

Only the shortfall gets ordered, from the supplier who already sells it to you, in time for the date it’s needed. The short delivery gets caught at the door, not at the kettle.

On the calendarMaterials landed 06 Aug · due 12 Aug
SUNMONTUEWEDTHUFRISAT
9
10
11RUNHalf the order
12RUNThe rest · due today
13
14SHIPFirst customer
15

The line never moves — only the schedule does. The run is placed where the kettles are free, behind the delivery that feeds it and in front of the date you promised.

The lot existsBecause the batch was logged — not written up later
FINISHED LOTSLV-6-0812-031,296 JARS
9 MATERIAL LOTS BEHIND IT
Shipped toJarsDate
Lone Star Grill Group48014 AUG
Mesa Market Foods57615 AUG
Bodega Norte24016 AUG

One entry at the top of this page became a buy list, a schedule, a lot code, three bills of lading and a costed month. Name that lot and the whole chain comes back — in both directions.

Documents produced  0 / 8
Bill of materialsWhat to buyPurchase orderProduction scheduleBill of ladingPacking listMonth-end countCost per jar
01  /  06  ·  Purchase order
Know what to make

Your orders are
your production plan.

Nobody should have to re-type a week of customer POs into another spreadsheet to work out what the line runs on Tuesday.

Open demand is read against the finished goods already on the racks and the safety stock you hold. What’s left is what has to be manufactured — turned into batches, run days and a place on the calendar.

Open customer orders
−Finished goods on hand
−Safety stock held back
=Jars to make · batches · run days
Production queue showing 10,428 jars to produce across 27 batches, with stock already allocated against the most urgent orders.
What’s left to make
Production calendar with runs placed on the days the kettles are free.
Placed where the kettles are free
01
Receive

It arrives. You scan it.

Every ingredient carries a QR tag printed off your own material list. Scan at the dock and it lands in inventory, against the right supplier, on the right date — with what actually turned up recorded against what was ordered, so a short delivery is caught at the door instead of at the kettle.

Raw materials list showing inventory value, item count and low stock flags.
102 ingredients, tagged
02
Plan

Will you have it by Thursday?

Open orders explode into everything they need and net against what's genuinely on your floor. The shortfall is the buy list — and you see what that buy costs before you commit to the run.

22Materials needed
9,600Jars to produce
13Short today
Bill of materials showing materials needed, jars to produce, shortfall items and estimated order cost.
On hand vs. needed
03
Produce

Log it once, at the kettle.

Finished goods go up. The raw materials it ate come down. The lot record writes itself and pH is captured against the batch while the operator is still standing there. No second entry — which is the only reason any of the rest of this can be trusted.

Production log listing batches by date, product, lot number and pH.
Inventory auto-deducted
04
Ship

The paperwork nobody pays you for.

A bill of lading is twenty minutes of retyping per shipment that no customer reimburses, and getting one wrong causes a delivery problem. Mark the order ready, ship it, invoice it — the paper comes off the record you already made.

Bill of ladingFrom the shipment
Packing listFrom the order
InvoiceOn ship
Purchase orderFrom the shortfall
Order list showing every purchase order with customer, PO number, jars, due date and status.
One row, every action
Station 05 — Trace

Name a lot. Any lot.

If a supplier recalled an ingredient lot tomorrow morning — how long before you could name every finished lot and every customer affected?

Most plants answer in days, and find out how long it really takes on the day it matters. Search by your lot code, by order, or by an ingredient lot when a supplier calls to say a batch was bad — every direction resolves the whole chain, dock to pallet.

← BACKWARD FORWARD → GJ-24081 GREEN JALAPEÑO · RECEIVED 08 AUG TM-24077 TOMATILLO · RECEIVED 06 AUG CV-24063 CIDER CIDER VINEGAR · RECEIVED 29 JUL FINISHED LOT SLV-6-0812-03 1,296 JARS · pH 3.96 LONE STAR GRILL 480 JARS · SHIPPED 14 AUG MESA MARKET FOODS 576 JARS · SHIPPED 15 AUG BODEGA NORTE 240 JARS · SHIPPED 16 AUG RECORDED AS THE WORK HAPPENED — NOT RECONSTRUCTED AFTERWARDS
A completed batch trace: finished lot, the batch that made it, six ingredient lots and the three shipments it went out on.
One lot code, the whole chain
06
Account

Close the month in an afternoon.

The numbers are already in there. Export them instead of spending two days assembling them out of spreadsheets.

Inventory valuationFor your accountant
Ingredient usageHow much of each
Average cost paidPer ingredient
Units builtPer SKU

That third line is worth more than it looks. Walking into a supplier negotiation knowing exactly what you paid per pound last month — against what you're being quoted now — is a different conversation than asking for a better price.

Monthly production tally showing units made, batches, estimated ingredient cost, units by product and ingredient usage with average price paid.
Everything valued, all the time

Know what it really costs
to make your product.

Recipes hold what a batch consumes. Ingredient prices, labour rates and monthly overhead are already in the system — so the cost of a jar is arithmetic you can quote from, not something you discover at year end.

Materials+ Labour+ Packaging+ Overhead= Cost per jar

Ingredient prices come off what you actually paid, not a list price from last year. Walking into a supplier negotiation knowing exactly what you paid per pound last month — against what you’re being quoted now — is a different conversation than asking for a better price.

Pricing and margins screen: overhead settings, a cost-per-jar breakdown of materials, labour, packaging and overhead, and the resulting gross margin.
Cost, sell price, margin

Built for one kind of plant.

Right for you if

  • You manufacture food or beverage and you’ve outgrown spreadsheets
  • You run real complexity out of one facility — multiple SKUs, recipes, ingredients and packaging
  • A handful of people cover ops, purchasing and QA between them
  • A customer or a retailer has started asking for traceability paperwork
  • You make your own brand, somebody else’s, or both

Not for you if

  • You’re already running a full process ERP and it works
  • You want accounting software — this runs the plant, not the books
  • You don’t manufacture — distribution alone doesn’t fit
  • One product, one recipe, one customer — a spreadsheet is genuinely still fine, and we’ll say so

If you co-pack for other brands, all of this runs several times over — a different set of recipes, materials, orders and lot codes per client, out of one facility. That’s where SupplyProLog is at its strongest, and it’s the operation it was built inside. It isn’t a requirement.

Built because we needed it.

Our first customer
was ourselves.

I’m Oscar Perez. I run a food manufacturing plant in San Antonio, Texas.

I was born in Reynosa and raised in McAllen, and I started the company in 2015 out of my grandmother Emma’s recipes. It began as one brand. Then came retail, then foodservice, then making product for other companies — and the operation got complicated faster than the spreadsheets could keep up with.

Orders came in by email. Inventory lived in a workbook. Production records were on a clipboard by the kettle. None of that information was missing. It was scattered — so every question anybody asked took an hour to answer.

SupplyProLog started as the system I wanted to run my own plant. A customer PO tells us what to make. The recipe tells us what that takes. Inventory tells us what we’re short. The batch logged at the kettle becomes the lot code, the shipping paperwork and the cost. Nobody enters anything twice.

We run the plant on it every day. Now we’re opening it to other manufacturers with the same problem.

Oscar Perez · Founder

Per plant.
Never per person.

Pick the tier that matches how many brands run through your plant — your own included. Every tier is one flat monthly fee for the facility, with as many people on it as the job needs.

Line$299 /mo1–3 brands in the plant

One facility, unlimited users on the floor.

Start setupEverything you need to run the line:
  • QR check-in at the dock, against the PO
  • Raw material and finished goods inventory
  • Recipes and bills of materials
  • Production log with lot codes and pH
  • Full backward and forward traceability
  • Bills of lading, packing lists, invoices
  • Month-end valuation and usage exports
Most plantsPlant$599 /moUp to 10 brands in the plant

One facility. Where most plants land.

Start setupEverything in Line, and:
  • Production calendar and scheduling
  • Shortage forecasting against open orders
  • Cost-per-jar engine with labour and overhead
  • Supplier price history and average paid
  • Customer and per-brand reporting
  • User roles for floor, office and QA
  • Priority support
Group$1,200 /moUnlimited brands, every site

Every facility you run, under one roof.

Start setupEverything in Plant, and:
  • Multiple facilities in one account
  • Cross-facility inventory visibility
  • Consolidated reporting across sites
  • Custom exports for your accountant
  • Onboarding run for each new site
  • A named contact who knows your plant
Per facility, never per seat

You need people on the floor scanning tags and logging runs. The moment a login costs money it gets rationed — and a half-entered record can’t be traced or costed.

Onboarding is quoted separately

We move you off the spreadsheets ourselves — your materials, suppliers, recipes and open orders, loaded and checked before you go live.

No percentage of what you make

A flat monthly fee. Your volume going up is your business, not a reason for your software bill to rise.

Doesn’t fit these three?

We’re still working out the right shape with our first customers. If your operation doesn’t land cleanly on one of these, tell us on the call and we’ll work it out.

Support that knows what a kettle is.

You are putting your traceability on this. Here is exactly what you get when something goes wrong, and who picks up.

Response timeSame day

Weekdays, Central time. In practice it is usually within the hour, because the person answering is the person who wrote it.

Mid-run problemsBy phone

If something breaks while a batch is in the kettle, you get a phone number, not a ticket queue. Production does not wait on email.

Getting startedWe do it

Materials, suppliers, recipes and open orders are migrated and checked by us before you go live. You are not handed an empty database.

What happens if the system goes down mid-run?
You keep making salsa. The floor process is a paper batch sheet at worst, and we backfill the records with you the same day — timestamps and all, so the lot is still complete for an audit. Nothing about a production run depends on a screen being up.
Who actually answers when I call?
Right now, the person who built it and runs a food manufacturing plant with it. That will not scale forever, and when it changes we will tell you rather than quietly putting a queue in front of it.
Can I get my data out?
Yes, whenever you like, without asking. Inventory, lots, production history and traceability records export to CSV and PDF. It is your data and your audit trail — holding it hostage would be a strange way to earn a renewal.
How long does onboarding take?
Typically one to two weeks from the go-ahead. Most of that is us loading your materials, suppliers and recipes and checking them against what is actually on your racks. The training itself is about two hours.
Will this pass an SQF or BRC audit?
The traceability records are built to be exported as an auditor-acceptable document, and mock recalls are what the trace screen is for. We are not going to promise you a certificate — the audit is about your plant, not your software — but the paperwork side stops being the hard part.
What if we outgrow it?
Then you should leave, and we will help you export cleanly. This is built for plants under about fifty people running real day-to-day complexity. Past that you want a full process ERP and we will say so.

Bring a lot number.
We’ll trace it live.

Thirty minutes. Pick any finished lot from your own plant and watch it come apart into every ingredient behind it and every customer in front of it. Then tell us how long that takes you today.

Eight questions so the call starts on your plant instead of on a slide deck. It takes about a minute.

— No sales sequence, no drip email
— Built inside a working food plant
— We’ll tell you if it isn’t a fit
Who we’re talking to

So the invite goes to the right inbox.

Your plant

Five questions. There are no wrong answers — we’re working out whether this fits you at all.

How many brands run through your plant? Count your own.

Roughly how many finished units leave the plant in a month?

What are you held to today?

Where do inventory and lot records actually live right now?

If a customer called about a lot in the next ten minutes, how long to answer?

What actually hurts

The part we’ll spend the call on.

Where does the most administrative time go? Pick as many as apply

What has actually gone wrong most recently?

Anything else worth knowing before the call? Optional — one line is fine

We have your answersNothing else to fill in — the call starts from what you just told us.

Last step — pick a time.

Thirty minutes, and bring a lot number from your own plant.

Rather do it by email? hello@supplyprolog.com

Thanks — we’ll be in touch today.

We reply the same day to book a time. If you’d rather not wait, copy the brief below and send it to hello@supplyprolog.com.