Business Challenge
The company needed one controlled B2B sales channel instead of maintaining ERP data, portal catalog, customer records and quote requests as separate systems.
Cases
ERPNextB2B CommerceSingle Source of TruthCustomer Portal
ERPNext-powered B2B commerce portal
Most B2B companies end up maintaining two systems: ERP and a customer-facing portal. That creates outdated prices, incorrect stock, duplicate customer management and manual content updates. Instead of maintaining separate systems, all product information, pricing, customer permissions, inventory, quotations and sales documents are managed entirely inside ERPNext.
Approach
The process was redesigned so the portal has almost no business administration of its own. It publishes ERP data for customers and returns quote requests, portal access and document visibility back into ERP workflows.
Business Impact
The business no longer manages two disconnected systems. Portal administration, catalog data, quotation requests and customer self-service are powered from ERPNext without a dedicated content manager.
Challenge Context
What made it difficult to manage
The company had a common B2B commerce problem: ERP contained operational truth, while the portal needed to present product information, availability, catalogues and customer actions to the market.
If those systems were maintained separately, employees would have to update products twice, keep pricing aligned manually, reconcile customer records and process quote requests outside the sales workflow.
For a B2B business, this creates real operational risk: customers see outdated availability, sales receives incomplete requests, marketing waits for portal edits and management cannot trust one source of commercial data.
The project therefore started with an architectural decision: the portal must not become another system to maintain. ERPNext had to own the business logic.
Why Standard ERP Wasn't Enough
A traditional ecommerce checkout did not match the sales process. B2B purchasing often requires negotiated pricing, stock confirmation, lead time confirmation, delivery planning and customer-specific conditions.
A standalone CMS would also create duplicate administration: product data in ERP, portal content in CMS, customer records in another place and quote requests in email.
Standard ERP catalog structure was not enough for customer navigation because operational item groups are designed for internal work, not for how customers browse a portal.
The correct architecture was not ERP plus portal. It was ERPNext as the business platform, with the portal acting as a controlled customer-facing layer.
Operational Workflow Design
Approach
The portal is not the system of record. ERPNext owns the business process.
This architecture turns ERPNext into the administration platform for the entire B2B commerce experience.
ERPNext was defined as the single source of truth for products, prices, availability, customers, quotes, orders, invoices and portal content.
The portal was intentionally kept as a presentation layer. It displays ERP-controlled data, captures customer intent and sends business events back into ERPNext.
Instead of a standard shopping cart, the B2B flow creates ERP Quotations. Sales can confirm pricing, availability, lead times and delivery terms before an order is finalized.
Customer-facing portal departments were introduced as a customer-facing catalog layer. One department can combine multiple operational item groups without changing ERP master data.
Before / After
Before
ERP maintained separately
Portal maintained separately
Duplicate customer management
Manual quotation processing
Inconsistent product information
Marketing changes required portal work
After
ERP controls the portal
Live catalog from ERPNext
Live pricing and availability
ERP quotation workflow
Unified customer portal
Portal content managed inside ERPNext
Solution Architecture
ERPNext owns the business objects. The integration layer publishes only the data and actions the B2B commerce portal needs for customer experience.
ERP-Controlled Architecture
How ERPNext publishes business data through an integration layer into the customer portal.
ERPNext
Products
Pricing
Inventory
Customers
Quotations
Sales Orders
Documents
Integration Layer
B2B commerce portal
Catalog
Customer Portal
Quote Requests
Order History
Documents
Quote-first Workflow
Why B2B requests become quotations instead of direct checkout orders.
Customer selects items
Request quote
ERP Quotation
Sales confirms conditions
Customer receives offer
Order can proceed
Customer Portal
How customers gain direct visibility into ERP documents.
Customer account
Portal access
ERP documents
Quotes
Orders
Invoices
Less manual PDF sending
Portal Control Center
Staff never update the portal manually. Every product, price, availability rule, catalogue, manufacturer logo and customer document is controlled from ERPNext without requiring a specially trained content manager.
| Area | Managed in ERPNext | Business purpose |
|---|---|---|
| Homepage | Content blocks and featured sections | Marketing updates stay controlled from ERP |
| Navigation | Menus and customer-facing departments | Customers browse by market logic, not internal ERP groups |
| Featured products | ERP product selection | Promotions use the same product data as operations |
| Catalogues | Downloadable files | Sales materials remain current |
| Manufacturers | Brand logos and visibility | Supplier presentation stays aligned |
| Access | Customer portal permissions | Customers see the right ERP documents |
Technical Architecture
ERP owns: products, pricing, inventory, documents, business rules and customer accounts
Portal handles: browsing, login, quote requests and self-service
Customer-facing departments translate operational item groups into customer navigation
Quote requests create ERP Quotations for sales review
Customer portal exposes ERP documents directly
Safeguards keep portal data aligned with ERP data
Operational Workflow
The process was redesigned so the portal has almost no business administration of its own. It publishes ERP data for customers and returns quote requests, portal access and document visibility back into ERP workflows.
1
Employees maintain products, pricing, availability, portal content and customer access in ERPNext.
2
The portal presents ERP-controlled catalog data through customer-facing departments and product pages.
3
A customer request creates an ERP Quotation instead of bypassing sales with a direct checkout order.
4
Sales confirms price, stock, lead time and delivery conditions inside ERPNext.
5
Customers use the portal to see ERP documents without employees manually sending PDFs.
6
Portal updates stay aligned with the operational system because ERPNext remains the source of truth.
Key Features
Scalability
The architecture can grow without turning the portal into a second back office. New departments, catalogues, featured products, customer access rules and quote processes can be managed through ERPNext.
Products
Categories
Inventory
Price lists
Customer groups
Customer-specific pricing
Quotations
Orders
Customer accounts
Documents
Availability
Attachments
Key Design Principles
ERP-driven pricing
Permission-aware catalog
Quote-only products
Real-time inventory visibility
Customer-specific portal visibility
ERP authentication
Document synchronization
Cache invalidation strategy
Business Impact
The business no longer manages two disconnected systems. Portal administration, catalog data, quotation requests and customer self-service are powered from ERPNext without a dedicated content manager.
No duplicate catalog maintenance.
No manual price synchronization.
Sales team manages the B2B channel from ERPNext.
Customers always see current availability.
Quote workflow is integrated with ERP.
Lower maintenance costs because the portal needs less separate administration.
Reduced risk of pricing errors.
Scalable architecture for ERP ecommerce integration, ERPNext ecommerce and ERP website synchronization.
Why It Matters
Many ecommerce projects duplicate business logic between the portal and ERP. In this solution, ERPNext remains the single source of truth while the B2B commerce portal focuses exclusively on customer experience. That is what makes it different from a standard Shopify to ERP connection.
What was connected
ERPNextB2B commerce portalProduct catalogPricingInventoryQuotationsCustomer portalPortal control center
Similar challenge?
Describe the current system and where time, data or control is being lost. The answer will show whether you need ERPNext, an integration, a website improvement or a simpler solution.
View services