WebMannaWEBMANNA / DIGITAL CRAFT
B2B & Wholesale Store
Separate public product information from partner terms so wholesale buyers see the right rules without exposing private prices.
Discuss your projectWhat we plan and deliver
We define buyer roles, access approval, ordering units and agreement steps. Partner pricing, credit terms, minimum quantities and documents require approved rules. The catalogue can end in a configuration request where automatic checkout does not match the sales process.
What determines the quote
Customer groups, pricing complexity, account features and accounting exchange are the main factors. Permissions, partner imports and approval journeys are assessed separately. A retail basket is not a complete B2B solution when additional business rules are required.
How the work is accepted
Tests compare a product under different roles, restricted documents and unusual order quantities. Private terms must not appear on public pages. Ownership of access approval and price maintenance is agreed before launch.
Service scope
Pricing varies by project scope. After a short brief, we provide a fixed quote based on complexity, content readiness and required integrations.
How it differs from retail. In retail there is one price for everyone. In wholesale every partner has their own, set by tier, volume or negotiation. The store has to show each buyer their price and only theirs. That changes catalogue logic, cart logic and ERP exchange at the same time.
What is usually needed. Customer roles with their own price lists, prices visible only after approved registration, minimum quantities and multiples, quick order from a list of SKUs, an account area with order history and documents, payment terms, and live stock levels.
Quick order is underrated. A wholesale buyer does not browse. They have a list of SKUs and need to paste it into one field and get a cart. Stores without that simply do not get used — buyers keep sending orders by email.
What drives the timeline. Not product count, but the ERP exchange: how many fields sync, how often, and what state the documentation is in. We establish that in the first stage, before the contract.
Overview
Tiered pricing per partner, account area, minimum quantities.
Starting price
Price on request
02 / ARCHITECTURE
Every layer has a purpose.
We connect the task, the user journey and the technical foundation. Scope and priorities are agreed before implementation.
- 01Partners
- 02Terms
- 03Wholesale orders
03 / CONNECTION
Not separate parts. One coherent system.
The components work together around your business scenario. We agree how the solution will be checked and handed over, and what support is needed after launch.
The graphics illustrate the approach, not measured client results.