B2B portals since 2016 Self-serve B2B on Shopify Plus, wired to the ERP you already run. Contract pricing, credit limits, approvals and stock resolve live, at 6am, with nobody in the office.
Free · yours in 48 hours · no call required
| Product | Qty | List | Your price | Extended |
|---|
Live quick order pad. Add a line, change a quantity, paste a reorder.
B2B commerce built for
Your buyer is a maintenance manager with 40 lines to place before a shift starts. They already reorder everything else at 6am from a phone. The order desk is the last thing in their week that requires a phone call, a PDF, and someone else's business hours.
of B2B buyers are millennials or younger, and rank self-serve reordering above rep contact.
to key one order by hand, against pennies for the same order placed by the buyer themselves.
system of record. A portal that cannot read your ERP quotes the wrong price, and the phone rings again.
No password to reset, no account to create. Shopify's new customer accounts email a six digit code to the address you already have on file. The buyer is in before the coffee is done.
Every order he has ever placed with you, searchable, with a reorder button on each. Quantities and pack sizes carry over. Prices redraw against his contract, not against list.
The order posts to your ERP as a real order, against the real customer record, with the PO number attached. Stock, credit and pricing are validated where they actually live. This is the part every portal project dies on.
Company profile, users, spending limits, ship-to locations and the assigned price list, all editable by the customer. The permission model is Shopify's, so it survives your next audit.
Open invoices, terms, aging and a pay button. Payments reconcile back to the ERP the same day. Your AR team stops being a call centre.
We sent a six digit code to
m.chartrand@ridgelinemech.ca
Didn't get it? Resend code
| Order | Placed | Ship to | Lines | Status | Total | |
|---|---|---|---|---|---|---|
| #NS-48219 | 14 Jul 2026 | Sudbury Yard | 41 | Delivered | $7,412.60 | |
| #NS-47980 | 02 Jul 2026 | Timmins Shop | 12 | Delivered | $1,884.15 | |
| #NS-47744 | 18 Jun 2026 | Sudbury Yard | 38 | Delivered | $6,905.40 | |
| #NS-47512 | 05 Jun 2026 | Sudbury Yard | 7 | Partial | $942.00 | |
| #NS-47301 | 22 May 2026 | Chelmsford | 24 | Delivered | $4,120.85 | |
| #NS-47155 | 09 May 2026 | Sudbury Yard | 33 | Delivered | $5,663.20 |
| Invoice | Order | Issued | Due | Aging | Status | Amount |
|---|---|---|---|---|---|---|
| INV-90441 | #NS-47512 | 05 Jun | 05 Jul | 41 days | Past due | $942.00 |
| INV-90388 | #NS-47301 | 22 May | 21 Jun | 55 days | Past due | $5,248.29 |
| INV-90612 | #NS-47980 | 02 Jul | 01 Aug | 14 days | Due soon | $1,884.15 |
| INV-90755 | #NS-48219 | 14 Jul | 13 Aug | 2 days | Due soon | $7,412.60 |
| INV-90810 | #NS-48307 | 15 Jul | 14 Aug | Current | Open | $9,315.83 |
Sign in · account.northlandsupply.com
Companies, locations, buyer roles, price lists and net terms are first class records on Shopify Plus. On a licensed platform each one of these is a line item in a statement of work. That difference is most of the gap between a nine month build and a fourteen week one.
The buying organisation, separate from the people in it. Orders, terms and credit hang off the company.
Each site carries its own address, tax treatment, catalogue and payment terms.
Ordering, draft-only or admin. One person can buy for several companies.
Per order caps by buyer, with anything above the threshold routed for approval.
Fixed prices or percentage adjustments off list, assigned per company location.
Case quantities, increments and minimums enforced at the line, not in a footnote.
Net 15, 30, 60 or fixed date, with the balance visible to the buyer.
A rep builds it, the buyer accepts and pays it themselves. No PDF round trip.
Six digit codes to a known address. Nothing for your team to reset.
Shopify's checkout, with PO capture and terms, carrying the compliance burden.
Show a company only what it is contracted to buy, and hide the rest.
Where your rules do not fit the model, they run as your own code inside checkout.
What is not standard is your ERP. That is the part we build, and it is the part below.
Shopify's own B2B documentationWe do not copy your pricing into Shopify and hope it stays current. Every object has one owner, one direction of travel and one defined behaviour when it fails. Pick one and read the contract.
Reads reconcile nightly and on change. Writes are queued, idempotent and replayable, so a failed post is a retry rather than a phone call.
Shopify Plus Storefront · accounts · checkout This is the layer most portal projects underestimate. A price list that drifts, or an order that silently fails to post, puts your buyer back on the phone and costs you the trust the portal was built to earn.
Forty-two questions about your own business: who buys from you, what they pay, what they order, and what happens after they hit submit. Each one sits beside what that answer changes about the build, so by the end you know which parts of your operation set the number.
The cost of a B2B portal is set by your pricing model and your ERP write path, not by the storefront. The storefront is the only one of the three anyone demonstrates.
One email with the file. Fill it in before you talk to anyone, including us.
Forty-two questions, answered by you
The cost of a self-serve B2B portal is set by your pricing model and your ERP, not by the storefront. Score yours before anyone quotes you.
Section 01 · 10 questions
Identity and hierarchy. Every answer here decides how many records exist, who maintains them, and which system owns the customer.
| The question | What the answer changes | 012 | |
| 01.01 | Does one buying organisation ever hold more than one account number in your ERP? | Each account number becomes a company or a location. Duplicates reach the buyer as two balances. | |
| 01.02 | Can one person legitimately buy for more than one of your customers? | Shopify models a contact against several companies. Most ERPs model a contact against one. The gap is yours to close. | |
| 01.03 | Does your largest customer buy to more than one address, and does each address carry its own price? | Price lists attach per company location. Per-address pricing is configuration. Per-address anything else is code. | |
| 01.04 | Who inside the customer approves an order above a threshold, and does that person exist in a system today? | Spending limits and approval routing need a named approver record. If none exists, someone maintains it from launch. | |
| 01.05 | Do your customers require a purchase order reference on the order, or on every line? | Order-level PO capture is standard at checkout. Per-line references become custom line attributes and an ERP mapping. | |
| 01.06 | Should a buyer see orders placed by other people in the same company? | Visibility is a policy decision, not a default. Get it wrong and you either leak information or frustrate the account. | |
| 01.07 | Is every buyer contact in your customer master a person, with an address of their own? | A shared mailbox cannot hold a per-person spending limit, an approval role, or a passwordless identity. | |
| 01.08 | Do you sell the same item to trade customers and to the public? | One storefront serving both needs catalogue separation and price separation, decided before design starts. | |
| 01.09 | Do you have customers under a parent that negotiates centrally and buys locally? | The native model is company, then location. Two levels. A third level lives in your ERP and is mapped in deliberately. | |
| 01.10 | How does a new trade customer get an account today, and who approves it? | A self-serve application with an approval step is a build. A rep-created account is a process. Choose before scoping. |
Shopify Plus development store 48h from request to staff invite We stand up a real Shopify Plus development store with B2B switched on and the data already in it: one company account, two buyers on different spending limits, a contract price list, net 30 terms and a quick order pad. You are added as staff. You click through the whole thing yourself, with nobody on the call.
Two weeks. We map your pricing model, your ERP objects and the order paths your buyers actually use, then hand you a scope with fixed numbers. You keep the document whether or not you build with us.
