← All posts
'Custom software vs off the shelf for distributors: when to buy, when to build'
'Custom software vs off-the-shelf for distributors—keep ERP/WMS SaaS, build portals, pricing, credit, and mobile workflows that SaaS cannot fit.'
The custom software vs off the shelf for distributors debate is rarely about replacing NetSuite, Microsoft Dynamics 365 Business Central, SAP Business One, or a warehouse stack like Fishbowl, Cin7 Core, or Manhattan Active WM. For regional wholesale distributors in the US and EU, the real choice is which workflows stay licensed SaaS and which become a fixed-scope custom layer—buyer portals, account price lists, credit holds, React Native pick/POD apps, EDI X12 / EDIFACT partners, and CSR approval queues.
This post is for owners, ops leads, AR managers, warehouse supervisors, and technical founders who already live in QuickBooks Online or Xero for the ledger, Shopify Plus B2B or PunchOut for some accounts, and still run exception work in Excel. At Wolverine Solution we ship fixed-scope web apps, customer portals, mobile tools, and light LLM exception routing for that ICP—not greenfield ERP replacements.
If you found us via wolverine software, this is the decision framework we use in discovery: buy commodity systems of record; build the commercial and exception edges that actually differentiate you.
How do I choose custom software vs off the shelf for distributors?
Start with off-the-shelf for ERP, accounting, and core WMS/IMS. Add custom software only where SaaS locks you into permanent workarounds on pricing, credit, buyer portals, or mobile rules. Keep NetSuite, Dynamics, Fishbowl, or Cin7 as the ledger. Build a thin React/Next.js and PostgreSQL layer on AWS or GCP that reads and writes through APIs.
That order matters. Another horizontal SaaS for every pain point creates shadow systems. A custom stock ledger from scratch burns runway on problems vendors already solved with barcode scanners, lot tracking, and cycle counts.
Who should be in the room:
- Owner / GM (budget ceiling, fixed-scope vs open-ended project)
- AR / credit manager (holds, terms, overrides)
- Inside sales / CSR (price exceptions, order edits)
- Warehouse or DC lead (Zebra/Honeywell scanners, FEFO, ASN)
- IT or fractional CTO (Auth0/Clerk, Terraform, REST/GraphQL, SFTP)
[Internal link: how distributors cut order errors without replacing ERP]
When is off-the-shelf the right call for a distributor?
Off-the-shelf wins when the workflow is standardized warehouse or accounting math that a maintained product already encodes well—SKU on-hand, receipts, transfers, GL posting, basic reorder points, and carrier labels. Fishbowl, Cin7 Core, NetSuite Inventory, QuickBooks Commerce, ShipStation, and UPS/FedEx APIs win here because your team should not own that schema.
Buy (or keep buying) when most of these are true:
- The process matches the product’s happy path. One to three warehouses, standard UOM, no exotic catch-weight or private-label rules the SaaS cannot model without weekly admin heroics.
- Hardware and integrations already exist. Barcode scanners talk to the IMS; QuickBooks Online or Xero connectors ship with the vendor; EDI VAN partners are already certified.
- You will not staff engineers for the ledger. Ops can live in vendor UI; you do not want Postgres migrations for stock quantities.
- Failure mode is configuration, not differentiation. Training and a cleaner SOP beat a rebuild.
Typical “buy” stack for regional distributors:
| Layer | Common off-the-shelf choices |
|---|---|
| ERP / GL | NetSuite, Dynamics 365 BC, QuickBooks Online, Xero |
| Inventory / light WMS | Fishbowl, Cin7 Core, NetSuite Inventory |
| Shipping | ShipStation, carrier portals |
| Some B2B storefront | Shopify Plus B2B, vendor punchout catalogs |
Do not confuse “we hate the UI” with “we must rebuild the system of record.” Hate the UI? Add a read-only ops dashboard. Hate account-specific pricing and credit-release rules? That is usually a custom layer—not a reason to rip out the ledger.
When does custom software beat another SaaS license?
Custom software beats another SaaS license when the bottleneck is your commercial rules or cross-system exceptions—not commodity stock math—and configuration cannot remove repeated data entry, delayed approvals, or preventable ship errors. Fixed-scope custom portals and internal tools win when two or more high-cost workflows span ERP, WMS, CRM, and email without a clean product fit.
Build (or tightly customize) when you see patterns like:
- Account / branch / promo pricing that cannot live cleanly in the IMS price book without spreadsheet side-cars.
- Credit application → hold → first order paths AR will not trust in a generic storefront.
- Buyer reorder portals with saved lists, backorder visibility, and invoice PDFs while CSRs still own exceptions.
- CSR price-override approval before submit, with an audit trail finance accepts.
- Mobile proof (temperature photos, POD signatures, offline queues) that horizontal apps only half-cover.
- Staff copy the same order or customer data between NetSuite, ShipStation, and Outlook every day.
- A spreadsheet still controls a process that moves cash, inventory, or customer commitments.
What “custom” usually means on our engagements:
- React or Next.js portal / internal tool
- PostgreSQL for app state; quantities and invoices still sourced from ERP/IMS APIs
- Auth0 or Clerk for buyer and staff roles
- Hosted on AWS or GCP with Terraform when the client wants ownership
- Optional LLM exception triage later—with human-in-the-loop gates—not as the system of record
[Internal link: custom internal tools agency for wholesale distributors]
How should you decide module by module?
Decide module by module: buy if the work is commodity and has a healthy vendor ecosystem; build if the module encodes your contracts, credit policy, or buyer experience and SaaS would force permanent workarounds. Score differentiation, change frequency, and whether an API layer on top of a bought ledger is enough.
| Module | Default | Why |
|---|---|---|
| Stock ledger, receiving, pick/pack | Buy | Fishbowl / Cin7 / NetSuite already own barcode + locations |
| Accounting / GL | Buy | QuickBooks, Xero, NetSuite GL are the audit trail |
| Carrier labels / rate shop | Buy | ShipStation and carrier APIs are commodity |
| Account-specific price lists | Build (often) | Regional contracts change faster than SaaS price books |
| Credit holds + override audit | Build (often) | AR rules are your risk model, not a storefront feature |
| Buyer reorder / status portal | Build or hybrid | Key accounts demand self-serve; ERP UI is not buyer UX |
| CSR exception queue | Build (often) | Spans pricing, credit, inventory, and shipping status |
| Field sales / POD / temp proof | Build or specialized mobile | Offline + photo evidence rarely fits one SaaS cleanly |
| Full ERP replacement | Almost never first | Disruption dwarfs the portal/tool ROI for mid-market |
Cut line we use in workshops: if you can write acceptance criteria on one page and name what you are not building, it is a candidate for a 10–16 week fixed-scope engagement. If you cannot, buy time with process and a SaaS trial—or run a paid discovery week before any code.
For inventory-adjacent modules only, the narrower cut line is in [Internal link: build vs buy inventory tools for regional distributors].
What does a hybrid stack look like in practice?
A hybrid stack keeps off-the-shelf systems as systems of record and puts custom software at the edges—where buyers, CSRs, drivers, and AR actually touch exceptions. NetSuite or Dynamics stays truth for orders and inventory. A Next.js portal handles reorder and status. A small approval service gates price overrides. React Native covers warehouse or delivery capture that must work offline.
Concrete example (regional foodservice or wholesale distributor):
- Buyer opens the portal (Clerk login), reorders from a saved list with branch-level ship-to rules.
- Order posts to NetSuite via REST; credit hold blocks submit if AR flags the account.
- CSR sees exceptions in an internal queue—missing price, partial ship, FEFO lot conflict—not in email threads.
- Warehouse picks in the IMS; driver captures POD photo + timestamp in a React Native app; status syncs back for the buyer.
That is custom software around off-the-shelf platforms—not a rewrite of either. It is also how you stay portable across US and EU ops without pretending one horizontal SaaS knows every regional rebate, VAT OSS nuance, or private-label pack rule.
How much should a distributor budget for custom vs SaaS?
Budget SaaS as recurring license plus admin time. Budget custom as a fixed-scope build plus hosting and a thin maintenance lane—not an open-ended “digital transformation” retainer. For the mid-market distributors we serve, the useful comparison is annual SaaS sprawl and shadow-labor cost versus a one-time portal/tool scope with clear acceptance tests.
Directional ranges (US/EU mid-market; validate in discovery—do not treat as a quote):
- Another horizontal SaaS seat pack: often lower cash outlay up front, higher forever cost when workarounds remain.
- Fixed-scope buyer portal or internal tool (single workflow cluster): commonly a defined project in the tens of thousands USD range depending on ERP integration depth—not a multi-year ERP program.
- Hidden cost of “buy everything”: CSR hours reconciling NetSuite + ShipStation + spreadsheets often dwarf the license line item.
Kill criteria for a custom project: no named owner, no one-page spec, no freeze on scope, and no metric (order errors, time-to-approve override, portal adoption). Missing those? Stay on off-the-shelf and fix the process first.
FAQ
Is custom software worth it if we already pay for NetSuite or Dynamics?
Yes—when the gap is buyer experience, pricing, credit, or mobile capture rather than missing ERP modules you have not configured. Custom software should sit beside NetSuite or Dynamics 365 as an API-connected layer, not a second ledger. If the ERP already does the workflow with training, buy seats and SOPs instead.
Will a custom portal lock us into one agency forever?
Not if you own the code, hosting, and infrastructure-as-code. Prefer GitHub-hosted repos, Terraform on AWS or GCP, documented APIs, and a one-page runbook. Fixed-scope handoff with your IT or a successor shop is part of done—not an afterthought. Avoid black-box low-code that only the vendor can change.
Can we start with off-the-shelf and add custom later?
That is the default path. Stabilize ERP/WMS, measure the exception hours, then scope the highest-ROI edge (portal, credit gate, CSR queue, or POD). Starting custom-first for commodity inventory is how distributors burn budget. Starting SaaS-only for unique commercial rules is how they collect workarounds.
What should we prepare before a build-vs-buy workshop?
Bring three recent exception examples (email threads or screenshots), the systems of record list (ERP, WMS, shipping, accounting), who approves price and credit today, and a ceiling budget. We turn that into a one-page functional spec: screens, roles, integrations, and an explicit “not building” list before any sprint starts.
How is this different from hiring a general app agency?
Distributor work is integration- and rules-heavy: EDI, lot/expiry, ship-to matrices, AR holds. General agencies often ship a pretty UI that still dumps exceptions into email. You want a shop that designs the cut line against NetSuite/Fishbowl/Cin7 reality and freezes scope—so you get a compounding asset, not a demo.
CTA: If you are weighing custom software vs off the shelf for a specific distributor workflow—reorder portal, credit holds, CSR approvals, or mobile POD—book a fixed-scope discovery workshop with Wolverine Solution. You leave with a one-page spec, module cut line, and a build/buy recommendation you can take to your GM or board.
KPI / review: Organic clicks + assisted demo requests from this URL; target ≥50 GSC clicks and 2 qualified discovery calls by 2026-10-16.