Complex B2B Commerce
When ERP terms, product information and procurement systems come together, commerce needs a shared operational basis. Paul Wiegand illustrates the approach.
A business customer expects agreed pricing and reliable availability in the store. Procurement teams may also require punchout workflows. The data and rules often live in the ERP while product information is maintained elsewhere.
Discuss Your Use Case
THE CHALLENGE
A business customer expects agreed pricing and reliable availability in the store. Procurement teams may also require punchout workflows. The data and rules often live in the ERP while product information is maintained elsewhere.
WHEN DATA TRANSFER ALONE IS NOT ENOUGH
The challenge is not the commerce platform alone. It is the interaction of customer identification, ERP, pricing, product information and procurement systems. Data ownership and responses need to be defined instead of maintaining the same commercial terms separately in several systems.
HOW NEKOM CONNECTS THE WORKFLOW
Customer context determines the relevant terms. NEKOM coordinates the required data and process interactions; ERP provides the pricing and availability it owns. The store presents the appropriate information and orders continue into operations. At Paul Wiegand this architecture brings BigCommerce, SHOPMACHER and NEKOM together with ERP.
Conceptual diagram. Configuration, interfaces and supported workflows are agreed for each project.
THE ACTUAL PRODUCT
Authentic NEKOM application views. The visible information is test data. These views illustrate general functions, not a named customer’s production system.
NEKOM PIM
The visible master data includes SKU, name, product type, EAN, manufacturer, category and product image. Tabs lead to attributes, SEO, inventory, prices, quantities and logistics. Not every function is visible in this single open area.
NEKOM OMS
The detail view brings together status, order items, customer context, billing and delivery information. It illustrates operational handling after an order reaches NEKOM.
OPERATIONAL VALUE
SHOPMACHER’s role at Paul Wiegand illustrates the division of work: frontend and UX on one side, operational integration and orchestration through NEKOM on the other. The exact split is agreed for each project.
PLATFORM & INTEGRATIONS
Process orders from different channels centrally and connect them to ERP, warehouse and service.
02Organise product information for different catalogues, countries and sales channels.
03Create a technical connection between enterprise systems and operational processes.
04Give customers central access to orders and service information.
CUSTOMER EVIDENCE & CONTEXT
Paul Wiegand: more than 100,000 products, around 45% of order volume through the platform and four people managing the catalogue. These published figures describe this customer project, not universal NEKOM outcome guarantees.
Explore customer storiesOrganise attributes, variants, content and translations for every channel.
02Connect new commerce experiences to established enterprise systems.
03Bring your own warehouses and suppliers into shared workflows.
FOR BUSINESSES
Discuss your systems, responsibilities and the most useful first workflow with us.
Discuss Your ProjectFOR AGENCIES
Your commerce expertise and our operations platform: let’s define the right way to work together on your client project.
Become a Partner