Mobile
Your app, not ours
A native iOS and Android app for your buyers, published under your name and your icon. When a venue searches the store for you, they find you — not a platform they have never heard of with your logo somewhere inside it.
One app per distributor
Your name on the home screen
We could have shipped one app for every distributor on the platform. We decided against it, and the reason is your customers.
Published under your brand
Your name on the home screen, your icon, your splash. The app is themed from your tenant the same way your portal is, so a buyer moving between the two is never handed somebody else's brand.
Your buyers find you by searching for you
A single shared app would have been cheaper for us to ship and worse for you. Venues look for their supplier, not for the software their supplier runs, and an app store is one of the few places a distributor still gets found by name.
Submitted as part of your rollout
Signing, the store listing, screenshots and review are handled during implementation, under your developer account or ours. We plan the first submission with room for a rejection, because every app gets one eventually and it is better to expect it than to promise around it.
What is in it
The whole trading relationship, on a phone
Not a catalogue with a cart bolted on. The screens a buyer needs to run their ordering without calling your office.
The whole ordering flow
Catalogue with search and filters, order guides per venue, an order pad for fast repeat entry, cart, checkout and confirmation. Order history with the lines on each one, so a buyer can find what they bought in March and put it back in the cart.
Invoices and account, gated properly
Invoices, terms, addresses and the people on the account. A member who may order but not see money gets that refusal from the server rather than an empty screen, and the access level is judged per venue: a manager at one site and an ordering-only user at another sees exactly that.
Their own numbers
The same buyer analytics the portal shows, read from the same place and recomputed nowhere, so a phone and a browser cannot end up with two different figures for one quarter.
Applications and support
A prospective venue can apply for a trade account from the app without an existing login, and your resource library — spec sheets, allergen documents, price lists — is available to buyers who already have one.
Same rules as the portal
A phone that cannot disagree with your platform
Most ordering apps recalculate your trade rules on the device, and drift from them the first time a holiday moves a cut-off. This one asks the platform and shows the answer.
The server prices the order, not the phone
Checkout sends no prices at all. The cart already lives on the platform, and placing an order runs your trade rules, GST, freight, credit, stock allocation, the freight calendar and your approval rules. What comes back is what was recorded, so a phone cannot bill differently from the portal.
Only the delivery days you can actually reach
Checkout offers the days the account's own call day, freight day, cut-off and holiday list allow, and the app computes none of them — it reads the platform's answer. An order placed after cut-off is told which delivery it missed and which one it lands on, in your words rather than a generic warning.
Credit, before the last tap
An account approaching its limit, over it, or on hold learns that on the cart screen, in the sentence the platform wrote, with the place-order button disabled. The alternative is a refusal at the final tap that nobody saw coming, which is the worst possible moment to find out.
Access judged per venue, not per login
Someone who runs one site and pours coffee at another is an administrator at the first and an ordering-only user at the second. Switching venue moves their access with it, and the app says which venues carry no visibility of money before they switch rather than after.
Where it is today
The app is built and runs against the live platform: signing in, the catalogue, order guides, the cart, checkout, orders, invoices, the account and analytics all talk to the real backend, with a test suite of more than five hundred cases behind them. Two things are still being finished before a first release, and both are worth naming. Some screens still show a total the app worked out for itself rather than the one the platform will bill, which can differ on bundles, bonus lines and promo codes — no order is billed wrongly, because the server prices every order, but a buyer could be shown one figure and invoiced another. And no app has been through a store review yet, so the submission pipeline is planned work rather than a path we have walked. If you are evaluating us now, ask where it stands the week you ask; we would rather answer that than have you find out later.
In the meantime the storefront installs to a phone straight from the browser, with no app store step — see the storefront, or the feature checklist for every line answered the same way.
Want it under your name?
Tell us how your buyers order today and we will walk you through the app on your own catalogue, and what publishing it under your brand involves.