What a Supplier Dashboard Should Tell You Before 9 A.M.
A useful dashboard is not a wall of vanity numbers. Before the day gets noisy, it should tell a supplier what moved, what is at risk, and where margin is quietly leaking.
Read more
wallmarkets · Blog
Notes on selling, shipping, and running a store
Store operations, industry thinking, and product updates from the wallmarkets team.
13 articles
More articles
Why Branch-Level Delivery Windows Matter More Than Most Suppliers Think
A supermarket chain is not one destination. It is a group of branches with different receiving habits, time windows, and operational quirks. Treating them as identical creates avoidable friction fast.
Read moreKilling N+1 Queries in a Logistics Dashboard Without Guessing
Before optimizing, we added query counting, grouped the expensive work into aggregate queries, and cached the result with Redis fallback. The difference between 'works' and 'feels fast' was not subtle.
Read moreKeeping Multi-Tenant Data Safe in a Flask App Without Separate Databases
A `business_id` column is not a tenancy strategy. Here's how we made the active business explicit in session state, queries, caches, and tests so supplier data does not bleed across accounts.
Read moreHow We Rebuilt the Foundation Before It Collapsed
Before we could ship the B2B portal, we had to fix what we'd been ignoring: 18 months of UI inconsistency and pages making 47 database queries. Here's what the audit found and what we did about it.
Read moreThree Cubes: The wallmarkets Brand
Three interlocking cubes. People ask what they mean. The answer: every design choice was driven by a constraint - 16x16 favicons, dark mode, thermal printer output - not aesthetics.
Read moreWhy We Chose PWA Over a Native App
Our users are in the field, on their phones, at supermarket receiving bays. So why not a native app? The answer came down to one thing: update distribution.
Read moreWhat Gap wallmarkets Fills (And What It Deliberately Doesn't)
Food businesses delivering to supermarkets have two software options: ERP systems (too big) or spreadsheets (too fragile). wallmarkets is what goes in that gap - and here's exactly where the edges are.
Read moreWhat the First Week Actually Does
The first week has one job: get your current operation running through the system so you can see what you've actually been doing. Here's exactly what to do on each day.
Read moreThe True Cost of a Single Return Event
We asked suppliers to calculate their full cost per return - driver time, admin, credit notes, reconciliation. Almost none had the number. When they did the math, it was always higher than expected.
Read moreThe Route Your First Driver Planned Is Still Running
Most delivery routes were assembled, not designed. The same expensive mistakes show up in predictable patterns - backtracking, waiting, separate return trips - and most are fixable in an afternoon.
Read moreSmall Suppliers Don't Lose Accounts Over Product Quality
Supermarkets have a simple test for every supplier: does working with them create more admin work than it's worth? Most small producers don't realize they're failing it until the orders start shrinking.
Read moreThe Spreadsheet That Finally Broke
Every food supplier we talked to had the same spreadsheet. It worked at three accounts. It broke around eight. By twelve, it was held together by one person who couldn't take a day off.
Read more