Your own B2B portal for your counterparties
A single-supplier portal on your own domain and brand: the catalogue is open and visible in search, while prices and ordering are reserved for counterparties you have approved — each with their own terms. Orders, invoices, price requests, deal chat and 1C exchange come out of the box.
We hand the portal over in full: the program and all its files go into your own storage (on GitHub). You do not depend on us — you can develop it yourself or hire any developer to do it.
Source code in your hands
Your domain and brand
Standard rollout in 3–5 days
Instance licence
190,000 RUB
Rollout
from 25,000 RUB
Boxed version of Kup2B: its own B2B portal
Portal on your domain and server: open directory, closed prices and orders, exchange with 1C, source code with you, launch in 3-5 working days.
Video transcript
The boxed version of Kup2B is a B2B portal for your counterparties: on your domain, under your brand and on your server.
The directory is open and visible in the search, and prices and orders are received only by companies that you have opened. You bring new customers yourself: search, advertising, managers.
What the company receives: its catalogue with a tree of categories and properties, individual prices to each counterparty, orders and invoices, price requests, warehouses and shipping dates.
Prices are downloaded from Excel and CommerceML, and goods, balances and orders are exchanged with 1C. There are REST APIs and webhooks for your systems.
The source code is sent to your repository. You do not depend on anyone: develop the portal yourself or entrust any developer.
A typical launch takes three to five business days: deployment on your server, branding, documents for your details, importing price and training.
Write or call us: show the portal live and calculate what you need.
Not a shared platform — your own portal
Both bring new clients. The portal is an open site on your domain: its catalogue is indexed by search engines, and any company can register by tax ID and request access. The difference is whose traffic it is. Buyers come to the platform by themselves, but your catalogue sits next to your competitors'. In your own portal nobody sits next to you — yet the flow is yours to create: through search, advertising, your sales team, a link in an email signature or on a business card.
Kup2B Box — your portal
There is one seller — you. Every company in the system is your counterparty.
The catalogue is open and visible in search; any company can apply, but you decide who gets prices and ordering.
The catalogue, the classifier and the prices are entirely under your control.
The portal runs on your server; the data and the client base are yours alone.
Kup2B platform
Many sellers, a shared platform, you among the others.
Platform traffic is shared: a buyer comes for a product and picks among sellers.
A subscription plan, with no rollout and no server of your own.
A good fit when you need a ready flow of buyers without doing your own marketing.
Who it suits
A wholesaler with a steady base
Dozens and hundreds of counterparties, each on their own terms. Managers forward price lists and calculate discounts by hand.
A distributor with several price lists
Wholesale, dealer, retail chain — each with its own price level, discounts on categories and brands, volume tiers.
A manufacturer shipping to legal entities
You need a private portal under your own brand: the client sees the stock and the shipping date and places an order without a phone call.
What the portal can do
The portal runs on the same foundation as the Kup2B platform — two years of work on the details of B2B trade, not a prototype built to order. But it is not a stripped-down copy of the storefront: your own portal gives you tools a shared platform cannot have — your own classifier, per-category attributes, bulk catalogue operations and full control over who sees what.
Catalogue and search
Your own category tree, tags, brands, per-section attributes, a sidebar filter with ranges, and fast search with suggestions and typo tolerance.
Individual prices
Price lists, “percentage / fixed / discount” rules for a product, category, tag and buyer group, volume tiers, personal prices.
Orders and invoices
Cart, checkout, order statuses, an invoice with your company details, payment marks, repeat order, ordering by a list of SKUs.
Price requests (RFQ)
The client asks for a price on items missing from the catalogue or the price list — the conversation and the quotation stay inside the portal.
Warehouses and lead times
Several warehouses, working hours, a calendar of exceptions, picking capacity — the portal works out the readiness date itself.
Price list import
Catalogue and price import from CSV, XLSX and CommerceML — as a file, by link, from S3 or FTP, on a schedule.
1C exchange
Standard CommerceML 2 exchange: products, prices, stock and orders with no manual re-entry.
Deal chat
Conversation with a counterparty about an order or a price request — instead of email and messengers, with the history kept.
Admin panel
Companies and document checks, orders, invoices, reference lists, store metrics — in a closed section.
Notifications
Email, the bell in the dashboard, realtime and Web Push — about a new order, a payment and a message.
REST API and webhooks
An API with tokens and webhooks about order events — to integrate with your own systems.
App on a phone
The portal installs on a phone as an app (PWA): its own icon, opened pages work offline, push notifications, keyboard and screen reader accessibility.
A catalogue you curate, not just fill in
In most portals attributes are one big pile: a manager scrolls through a hundred fields to find the three that matter, and the buyer gets a filter that asks how many lamps a cable has. Here attributes belong to categories, and that changes the whole way the catalogue works — from the product form to the filter your client searches with.
Every category has its own attribute set
You decide what belongs to a section: cross-section and conductor material for cable, wattage and socket for a lamp. The set is inherited down the tree and you control the order. The product form shows only what is relevant.
Required attributes
Mark what a card cannot go without — weight, warranty, ingress protection. A product missing them is saved as a draft but never reaches the storefront. The catalogue stops filling up with blanks, because the portal checks it, not the manager.
A filter people actually search with
A number becomes a from–to range, a yes/no becomes a checkbox, a list shows values with product counts. Options leading to an empty result are not shown at all: the client keeps narrowing down and always finds something.
Bulk setup through Excel
With hundreds of categories nobody does this by hand: export the tree as one file, fill in attribute codes, upload it back. A single bad row cancels the whole upload — a half-configured catalogue never happens, and filled-in product attributes are never lost.
How it looks in the catalogue
| Section | Section attributes | In the client's filter |
|---|---|---|
| Cable | Cross-section · Conductor · Voltage | Cross-section, mm²: 1.5 to 6 |
| Lighting | Wattage · Socket · Colour temperature | Wattage, W: 10 to 60 |
| Fasteners | Diameter · Length · Coating | Galvanised: yes |
The same sets work in price-list import and 1C exchange: the run report tells you when a file brings an attribute that does not belong to the section.
How prices work in the portal
A counterparty price is calculated by rules rather than by a manager: a base price list, discounts on categories and brands, volume tiers and individual prices. A guest can be shown no price at all.
| Who is looking | Rule | Sees |
|---|---|---|
| Guest | Prices hidden by a setting | Price after sign-in |
| New counterparty | “Wholesale” price list | 1,000 RUB |
| Dealer | “Dealer” price list, −7% on the brand | 930 RUB |
| Retail chain, from 100 pcs | Volume tier | 880 RUB |
What it costs
The price splits into two lines: the right to use the instance and the work of launching it. They go separately in the contract and in the invoice.
Instance licence
190,000 RUB
A non-exclusive licence for your instance of the platform — a fixed price. The code is handed over to your repository: the instance, the data, the domain and the brand are yours.
Rollout
from 25,000 RUB
Deployment on your server, branding, legal documents under your company details, reference lists, import of one price list and training.
The personal-data operator document pack (notice to the regulator, order appointing the responsible person, internal policies) is a separate service: from 90,000 RUB
The documents are drawn up by practising lawyers, and the price is their work rather than our markup. So, plainly: if you have a lawyer of your own, hand these papers to them — they know your business from the inside, and it will be faster and cheaper. Our service is for those who have no one else to turn to.
What the price includes
Handover of the code to your GitHub — the repository belongs to you.
Deployment on your hosting: docker compose, database, Redis, search, S3, queues, cron, SSL.
Domain and branding: logo, palette, name, email templates — up to 2 iterations.
Your legal entity details put into the offer, the privacy policy, the rules and the invoices.
Setting up the first administrator, reference lists, warehouses and delivery methods.
Import of one catalogue or price list in one format (CSV, XLSX or CommerceML).
Two hours of training over a video call, plus the recording.
A 60-day warranty on rollout defects.
What is beyond the price
This work is not included, but we take it on against a separate invoice — except for external services, whose bills are yours in any case.
Hosting, domain, S3 and external services — the accounts and the bills are yours*
Logic changes, new fields and integrations beyond the standard ones*
Custom design beyond a change of logo and palette*
Data migration from your previous system*
Setting up 1C on your side*
Support and changes after the acceptance certificate is signed*
* We do it for a separate fee: we estimate the work in hours and issue an invoice before the start. The accounts and payments for hosting, the domain and external services are arranged by you — we will help to set them up.
How the launch goes
The order of steps is fixed and the scope of work is closed — that is why a standard rollout fits into 3–5 working days.
Payment and questionnaire
After payment we send the onboarding questionnaire: domain and access, company details, logo and colours, the catalogue with its attributes, warehouses and the rules for working with counterparties.
Building the instance
We take a snapshot of the current code base and build your installation from it.
Repository
The code goes to your GitHub, the rights to the repository are yours.
Deployment
We bring the portal up on your server and connect email, S3, the captcha and company lookup by tax ID.
Branding and documents
Logo, palette, emails; the offer, the policy and the consents — under your company details.
Filling it in
Reference lists, warehouses, delivery and payment methods, import of your price list.
Training
Two hours over a video call, recorded: catalogue, prices, orders, counterparties, admin panel.
Acceptance and sign-off
We go through the acceptance protocol and sign the acceptance certificate. The 60-day warranty starts from it.
What we need from you
All of this is prepared before the work starts — following the questionnaire we send after the payment.
Server
A VPS with Docker, at least 4 vCPU and 8 GB of memory. Shared hosting will not do: PHP 8.4 with Octane, PostgreSQL, Redis, Meilisearch and Reverb.
External services
A domain with DNS access, two S3 buckets (images and documents), SMTP for email, phone confirmation by call, company lookup by tax ID, and a captcha.
Documents and brand
Your legal entity details, a vector logo and brand colours.
Frequently asked questions
Let us talk about your portal
Write or call — we will tell you more, show the portal live and work out what exactly you need.
hello@kup2b.ru · +7 495 128-97-96