Most operators we talk to already run something. A spreadsheet that's been refined over years, an ordering portal their customers know, a routing tool they like, an accountant who wants the numbers in a particular shape. The question underneath "can we try Drofilla" is usually a quieter one: if I put my operation in your system, can I still get it back out.
Yes. That's what API v1 is.
What it is
Twelve read endpoints covering orders, routes, products, customers, staff, and warehouse locations. You get an API key from your Drofilla admin, scoped to exactly the data you want the integration to touch — orders only, or orders plus customers, or everything. The key determines which company's data it can see, and there is no parameter that changes that. Revoke it and the integration stops.
The full reference is at docs.drofilla.com. The spec is OpenAPI, so most code generators will build you a client from it directly.
Catching what the intake missed
Order intake at most 3PLs is email, and email is messy. A purchase order arrives in a format nobody has seen before, an attachment doesn't parse, a customer sends to the wrong address. Drofilla's AI intake handles the overwhelming majority of it, and the honest answer is that no intake system handles all of it.
So verify. Pull tomorrow's orders by delivery date, compare against whatever your own source of truth is — the inbox, the distributor's portal, a shared sheet — and flag the gap. One of our operators runs exactly this at 1:30 in the morning. If something didn't land, the team knows before the pickers arrive rather than when a restaurant calls at eleven.
Getting numbers where your accountant wants them
Every order carries its financial breakdown: subtotal, delivery charge, tax, total. Cost, margin, and net revenue sit behind a separate finance scope, so you can hand a bookkeeper a key that reads invoicing figures without exposing what you make on each order.
Filter by payment status, by warehouse, by delivery date range, page through the whole history. That goes into your accounting system on whatever schedule you want, in whatever shape your accountant has always used.
Route performance, honestly measured
Each route returns planned and actual start and end times, planned and actual distance, and a count of stops completed, failed, and skipped. Each stop carries planned versus actual arrival, service time, and distance from the previous stop.
That's enough to answer questions most operations run on guesswork. Which customers take twice as long to serve as the plan assumes. Which routes lose their schedule at a specific hour. Whether the third stop of the day is where the day goes wrong. If you're still routing with another tool, you can pull Drofilla's actuals and score your own plan against what really happened.
Customer and catalog records that match your other systems
Customers come back with their member ID — the same identifier your distributor uses. That's the join key between Drofilla and whatever you already run, which means customer records can be reconciled instead of re-keyed.
Products come back with their UPCs, category, brand, storage class, and units per case. Match your catalog against the distributor's, find items missing identifiers, spot duplicates before they cause a picking error.
Dashboards nobody has to log in for
A store manager who wants today's numbers shouldn't need a seat in an admin panel. Pull orders filtered to their warehouse, their date, their statuses, and put it wherever they already look — a morning email, a wall screen, the sheet they use anyway.
Staff records return names, roles, and warehouse assignments, so headcount and coverage can feed the same view. No pay data leaves through the API.
Building with an AI assistant
The spec is machine-readable, which turns out to matter more than we expected. Point Claude or a similar assistant at it and describe what you want in plain language — one of our customers built their overnight reconciliation job this way. The assistant reads the endpoints, writes the client, and handles the pagination.
We'd rather that than sell you an integration.
What it doesn't do yet
Read only. You can pull anything, push nothing — order creation through the API is scoped and not yet built. No webhooks either, so integrations poll on whatever interval suits them, within a rate limit that's comfortable for the automation jobs we've seen.
Both are on the list. We'd rather ship a small surface that's correct than a large one that isn't.
Getting a key
Talk to us. Keys are issued per company and per scope, and we'd rather understand what you're building first — partly to scope the key correctly, partly because your integration usually tells us something about the product.
Or email contact@drofilla.com.