Skip to content

Kentro Storefront · B2B wholesale portal

A B2B portal where every wholesale buyer sees their own prices

Wholesale customers sign in, see the price list you assigned and order on their own, by card or on net terms. Each order lands in Kentro OS on the same stock as Shopify, Amazon and EDI. You set the store up yourself, in a customizer in Kentro OS.

  • Card or net terms at checkout
  • A price list per customer or tier
  • Invite codes and applications
  • Included in every Kentro OS plan
A wholesale buyer ordering at their own prices

What is a B2B portal?

A B2B portal is a private online store for wholesale customers. Buyers sign in, see the prices and products set for their account, and place orders without calling or emailing a sales rep. The Kentro B2B portal runs on Kentro OS, so a wholesale order uses the same stock, invoices and fulfillment queue as every other channel.

The B2B portal

What the B2B portal does

Pricing, access and ordering for wholesale buyers, on the same records as the rest of Kentro OS.

A price list for each customer or tier

A price list adjusts prices for every product, for chosen categories, for tagged products or for single products. Assign it to a customer, and that buyer sees those prices when they sign in.

  • Adjust all products, categories, tags or single products
  • Minimum and maximum order amount per list
  • Minimum and maximum quantity per SKU
  • Hide products a tier should not see
  • A rounding rule for adjusted prices
A wholesale price list with order limits

Invite codes that set the terms before a buyer orders

An invite code carries the price list, order limits, tax exemption, shipping rule and sales rep for whoever redeems it. Send one code to one buyer, or generate a batch before a trade show.

  • One-time, multi-use and batch codes
  • Price list, order limits and credit limit on the code
  • Tax exempt and free shipping options
  • A use count on every code
An invite code that carries a price list and order limits

Applications you approve

A prospect fills in the application on your portal, and it lands in Kentro OS as pending. Approve it, assign a price list, and the buyer can order. Reject it, and they cannot.

  • Pending, approved and rejected applications in one list
  • An approved applicant becomes a customer in Kentro OS
  • Assign a sales rep and tax settings on the customer record
Wholesale applications ready for you to approve

Ordering and accounts buyers run themselves

Buyers browse the catalog at their prices, fill a cart and check out. They keep their own addresses, look up past orders and can put a regular order on a subscription plan you define.

  • Catalog, cart and checkout
  • Order history and order details
  • Saved addresses and account details
  • Subscription plans for recurring wholesale orders
  • Coupons with a minimum and maximum order value
A wholesale buyer browsing the catalog at their prices

Orders land in Kentro OS with every other channel

A portal order draws on the same stock and ships from the same warehouse as a Shopify or Amazon order. Its invoice and payment sit on the customer record your team already works from.

  • One stock count for wholesale and retail
  • Invoices and payments on the customer record
  • The same pick, pack and label flow
Ecommerce order management
A wholesale order in the fulfillment queue beside marketplace orders

Credit limits and net terms

Credit limits are checked at portal checkout, so they are enforced in part

Set a credit limit on a price list, on an invite code or on the customer record, and net terms in days on the customer. When a buyer with a credit limit checks out on terms, the portal adds up their unpaid invoices and refuses an order that would take them past the limit.

That check runs at portal checkout. Do not count on it for orders your team enters by hand in Kentro OS: look at the customer’s open balance before you release those.

  • Credit limit on a price list, an invite code or a customer
  • Net terms per customer, in days
  • Checked against unpaid invoices when a buyer checks out on terms
  • Hand-entered orders: your team checks the balance
A customer record with a credit limit and net terms

Kentro Storefront

The store around the portal

The B2B portal is part of Kentro Storefront, built on the Store API. These come with it on every Kentro OS plan.

A customizer you run yourself

Start from one of three templates (Classic wholesale, Brand story or Catalog first), arrange the home page in sections, add pages and menus, set your logo and publish from Kentro OS.

Access rules per store

Choose who can buy and who can sign in, whether visitors can browse the catalog, and whether they see prices before they sign in.

Invoices buyers can pay online

Buyers see their invoices in their account and pay one online, without a call to your accounts team.

A domain you verify

Publish the store on a managed address, or verify a domain you own in Kentro OS and serve the store from it.

Cookie consent and tags you control

Set a cookie consent banner by region and add your Google Tag Manager container from the customizer.

The Store API under it

The storefront is one client of the Store API. Your own site or app can use the same buyer sign-in, catalog, cart and checkout with a storefront-scoped key.

Limits

What the B2B portal does not do

Better to read this here than to find it in week two.

A credit check at portal checkout, not on every order

The credit limit is checked when a buyer checks out on terms in the portal. Do not count on it for orders your team enters by hand in Kentro OS.

No returns workflow

A buyer cannot file a return in the portal. Kentro has no returns or RMA workflow; your team handles returns with credits and refunds in Kentro OS.

No marketplace of buyers

The portal is your own ordering site for the accounts you sell to. It does not list your products to new retailers, and Kentro has no native Faire integration.

No point of sale

Kentro has no point of sale. The portal takes orders online, by card or on net terms.

One job, three ways

Review a wholesale account before you raise its credit limit, three ways

Review a wholesale account before you raise its credit limit

  1. In the app

    Open the customer in Kentro OS. The price list, credit limit and net terms are on the record, next to the customer’s orders. Change the limit there.

    A wholesale customer record in Kentro OS
  2. With Kentro AI

    Ask "How much has Northside Supply ordered this year, and what is still unpaid?" Kentro AI answers from live orders and invoices and links the records. It reads. You change the limit.

    Kentro AIIn Kentro
    1. you ›How much has Northside Supply ordered this year, and what is still unpaid?
    2. runSqlQueryRead this customer’s orders and open invoices for the year (read-only)
    3. Here is the order total by month and the invoices that are still open, oldest at the top. Each row links to its record.

  3. With your agent

    Your agent asks the same question over MCP, signed in as you, and gets the same answer. No MCP tool places an order or changes a credit limit. Buyer-side ordering for agents runs on the Store API.

    ClaudeConnected to Kentro over MCP
    1. you ›Before I raise the limit for Northside Supply: what do they owe us?
    2. askCopilotHanded the question to Kentro AI, with your permissions
    3. Two invoices are open. The older one is past its terms. Changing the credit limit happens in Kentro OS.

Questions about the B2B wholesale portal

What does the Kentro B2B portal include?

Price lists, invite codes, applications, buyer accounts and self-serve ordering by card or on net terms, with every order landing in Kentro OS. Kentro Storefront, built on the Store API, adds a customizer you run yourself in Kentro OS, access rules per store, online invoice payment and an API for your own front end. All of it comes with every Kentro OS plan.

How do price lists work for different wholesale customers?

A price list adjusts prices for all products, for selected categories, for tagged products or for single products, with a rounding rule. It can also carry a minimum and maximum order amount, quantity limits per SKU and a list of products to hide. Assign a list to a customer directly, or attach it to an invite code so the buyer gets it when they sign up.

Can I limit how much a wholesale customer buys on credit?

Yes, at portal checkout. Store a credit limit on a price list, an invite code or the customer record, and net terms on the customer. When that buyer checks out on terms, the portal adds up their unpaid invoices and refuses an order that would pass the limit. The check covers portal checkouts. Orders your team enters by hand in Kentro OS are for your team to check, so the limit is enforced in part.

What happens after a buyer places an order in the portal?

The order appears in Kentro OS in the same queue as orders from Shopify, Amazon, TikTok Shop and EDI. It draws on the same stock and ships from the same warehouse with the same labels, and its invoice and payment sit on the customer record. If QuickBooks is connected, invoices and payments sync to it. Nothing is exported or imported between the portal and operations.

Does the B2B portal replace Faire or my EDI connections?

No. The portal is your own ordering site for accounts you sell to directly. Retailers that require EDI keep ordering through SPS Commerce, which Kentro OS connects to. Kentro has no native Faire integration, so Faire orders are not imported automatically. Portal orders and EDI orders meet in Kentro OS on one stock count.

What does the B2B portal cost?

The B2B portal is part of Kentro Storefront, which is included in every Kentro OS plan, from $500 a month. There is no Storefront add-on to buy. Kentro OS is required, because the portal sells from its products, prices and stock, and its orders go to the same fulfillment queue.

Give wholesale buyers their own ordering site

The B2B portal is part of Kentro Storefront, included in every Kentro OS plan. Tell us how your wholesale buyers order today.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy