Platform

Three ways an order arrives. One place it lands. Platform overview

How orders arrive
B2B StorefrontLet customers order themselves, at their own prices Email order capture VisionCapture any email, file or photo into digital orders EDI orders Turnkey EDIReceive EDI orders without the development work

Included with every plan
Plain-language automation Tippy AIAI operator that does the admin work Email marketing automation PulseTurn buying signals into follow-up ReportsPlain-English questions about your data

For reps who sell by phone and in person
Quotes and orders for reps Orbit NewSales workspace that tells reps where the next order is
€49/seat/mo, minimum 3 seats. Runs alongside a channel plan rather than on its own.

Customer stories Integrations Turis vs Shopify Plus
Book a 30-min demo
Integrations
Pricing
Customers
Resources

Learn
Guides and articles How wholesale brands run B2B ordering. Encyclopedia Plain definitions of the B2B terms.

Product
What’s new The latest features shipped on Turis. Help centre Guides, how-tos and product docs. API documentation Endpoints, auth and webhooks.
About

Book a 30-min demo Start free trial 14 days, no credit card needed. Sign in

B2B Storefront For the customers who will order themselves

Every retailer sees their own price, and orders it themselves

They can order at eleven at night, without asking anyone what their price is.

Book a 30-min demo Start free trial

Live product, your order flow, no slide deck. · Trial: 14 days, no credit card needed.

Work it out on your own numbers

Three you already know.

How many price lists are you keeping correct?

One per customer group, plus the one-offs you agreed on a call, plus whatever went out as a PDF last season. Count the versions in circulation. Now count how many are still right.
How many times last week did someone ask what their price was, or whether something was in stock?

Every one of those waited for you, or for somebody here, to be free.
How many orders arrived through a person rather than a screen?

Multiply by the minutes it takes to enter one, divide by 1,600 — roughly a working year — and you have it in people.

A storefront that already knows each customer’s prices removes all three: the lists stop being maintained, the questions stop being asked, and the order arrives entered.

The buyer’s side

Re-ordering in less than 60 seconds

Your customer signs in on your website and sees their own catalogue, at the prices you set for them. They open “Order again”, drop last month’s order straight into the basket, and add a few more items by typing part of an item number. Then three things happen that a consumer webshop cannot do at all.

Three things a consumer webshop has no concept of — case sizes, a volume break the buyer sees before committing, and their own purchase order number travelling with the order.

Your brand, not our template

It should look like you, not like us

Your buyers should not be able to tell which platform you run — they should see your shop. Layout, colours, type, navigation, banners, the order of the product grid and what appears on a product card are all yours to change, in the interface, without booking anyone.

Two Turis storefronts. Different navigation, different colours, different language, different density — and neither brand wrote a line of code or booked a developer to get there.

You do all of this yourself

Page layout, section by section, from blocks named after the things a wholesale page needs — SKU, RRP, variants, stock level
Or skip the building: describe the page you want in a sentence and it gets built for you
Colours, logo, type and the navigation your buyers see
What sits on a product card, and the order products appear in
Every word on the buyer side, in any of the languages you run

Can it handle our complexity

What wholesale actually requires

A retail webshop has one price, sells in ones, and takes cards at checkout. Wholesale has none of those luxuries. Here is what that means in practice — starting with the three that decide deals.

Prices and visibility

Every customer has their own prices — and their own catalogue

Every customer can have their own price on every product: per customer, per group, per product group, overridden at any level, and as many separate agreements as you have actually negotiated. Those same prices decide the catalogue — a product with no price for that account is invisible to that account, so private-label lines stay private with no second permissions system to drift.

Volume breaks the buyer sees in the basket, before committing
Automatic discounts on conditions you set, stacking in an order you control
Show a retailer their own margin on the product page
Leave the price blank and the product does not exist for them

One screen decides both what Sundal Retail pays and what Sundal Retail can see — a product with no price on their list does not exist for them.

Preorder and stock

Sell the season before it exists

A buyer commits to autumn in March, split across an August and an October drop, each window with its own minimum, at prices held from the day they signed. That is the difference between a preorder engine and a spreadsheet called AW26_commitments_FINAL_v3.xlsx.

Backorder, with the expected date on the line as they add it
Stock held while an order is approved — the last twelve units cannot sell twice
Quotes that convert to orders with no re-keying
Subscriptions the customer pauses, adjusts and skips themselves

A buyer commits to autumn in March — split across an August and an October drop, each with its own minimum, priced when they signed.

Express Ordering

The buyer who prefers Excel keeps Excel

Some buyers will never browse a catalogue, and they do not have to. They paste their spreadsheet — or upload the CSV — and the basket fills itself at their prices. You get a clean order; they never change how they work.

A half-typed product code still finds the right product
Barcode scan-to-add — restock from the stockroom shelf with a phone
Saved baskets, and lists shared across the buyers on an account
Search that copes with typos and partial part numbers

The buyer who prefers Excel keeps Excel — the paste fills the basket, at their prices, and a half-typed code still finds its product.

The rest of the list

And then there’s everything else

None of it needs a full section. All of it is the difference between a webshop and a wholesale operation — so it is all here, one line each, documentation one click away.

Minimum order quantities

Per product, overridden per customer where you agreed otherwise.

Pack and case sizes

Cases of 24 means the basket only allows 24s — and says so on the line.

Minimum order value

A floor per customer, with the basket showing how far off they are.

Credit terms per customer

NET 30, NET 60 or up front — set per account, shown at checkout.

Credit limit blocking

Orders stop before the goods ship, not after the invoice bounces.

Purchase order capture

The buyer’s PO number travels into your ERP, so your invoice gets paid on time.

Tax by where the buyer is

VAT by country and status, including reverse charge inside the EU.

Shipping rules to the postal code

Zones, rates and carriers — the island surcharge enforces itself.

Multi-region storefronts

One back end; per-region language, currency, price list and tax.

180+ languages on the buyer side

The Portuguese pharmacy chain orders in Portuguese. You translate nothing.

Dropshipping with its own prices

Ship direct to their end customers — dropship terms never leak into trade terms.

Multi-site accounts

Nine shops, one parent account. Each orders for itself; you see all nine.

Sign-off before an order is placed

Held until the named approver approves — an unapproved basket is never an order.

Stock per warehouse, per buyer

Each customer sees the availability that is actually theirs.

Exports with the paperwork’s fields

HS codes included — the freight forwarder’s spreadsheet comes out of Turis.

After they press order

It lands in your ERP with nothing to re-key

An order placed in the storefront arrives in your ERP — the system holding your stock, prices and invoices — with the customer, the products, the agreed prices, the tax treatment, the delivery address and the PO number already attached. Nobody re-keys it, which means nobody mistypes it.

Native connections to Microsoft Dynamics 365 Business Central, SAP, Infor M3, Visma Net, Rackbeat, Uniconta and Xero. Anything else connects through our API or a flat-file import, and we will tell you on the first call whether yours is straightforward, a project, or a bad fit. See all integrations →

And when you need the data out rather than in: product and order exports carry the fields the paperwork actually needs — including HS codes for customs — so the freight forwarder’s spreadsheet comes out of Turis instead of being assembled by hand.

Technical detail — what happens when the ERP is down, and how it is secured

If your ERP is unavailable: Orders are accepted in the storefront and queued, then written when the connection returns. A buyer’s order is never lost because your back office is down.
Security and compliance: SOC 2, ISO 27001, and a 99.99% uptime SLA.
Getting connected: The first ERP connection is ours to make, as part of implementation and support through to go-live. It is not a fee and it is not an upsell.

Anything below this level of detail — sync intervals, field mapping, single sign-on, where your data is hosted — is a question for the call, and you will get a straight answer rather than a brochure.

Before you ask us

The questions that come up first

In roughly the order they get asked. The big one — will our customers actually use it — has a section of its own further up, because a line in a list was never going to be enough.

Do our customers have to log in to see prices?

Yes — and that is the point. A signed-in buyer sees the prices agreed with them, never a “contact us for trade rates” wall. You can also switch on a public version that Google indexes, showing your standard price list, RRP or no prices at all, with a form for new retailers to apply.

What about the customers who will never use a portal?

They keep emailing, and Vision reads what they send — PDF, spreadsheet or plain text — and turns it into an order in the same list as the portal orders. You do not need every buyer to log in; you need every order to arrive the same way.

Can it handle our pricing? It is complicated.

Per customer, per customer group, per product group, with volume breaks, and with automatic discounts on conditions you set, stacking in an order you control. A blank price on a customer’s list also hides the product from them, which is how private-label lines stay private.

Do we need a developer?

Not for the shop. Layout, colours, navigation, the product card and every word on the buyer side are yours to change in the interface — or you can describe the page you want and have it built for you. A custom domain and the first ERP connection are ours.

How many users do we get?

No per-user charge and no seat count to manage. Turis is priced by order channel, so putting your whole team in it costs the same as putting one person in it.

How long until we are live?

It depends on how clean your product and customer data is, and we would rather look at yours than quote you an average. Implementation and support all the way to go-live.

What does it cost?

From €299/mo, priced on the value of orders that go through the storefront. No setup fee, no commission and no per-user charge. The full ladder →

What if we outgrow you?

Your data is yours, and it comes out two ways: a full CSV export of products, customers, prices and order history, and the API, which is the same one the platform runs on. 12 months, and there is no exit clause to negotiate because there is nothing to exit.

See it with one of your own orders

Send us a real purchase order — a messy one, ideally — and we’ll show you what Turis does with it on the call.

Book a 30-min demo Start free trial

Live product, your order flow, no slide deck. · 14 days, no credit card needed. · No commission on your sales, ever.