Skip to content
Studio Beltramelli

Typical scenarios

Every project is unique because every company has its own systems, logic and goals. Below are some typical cases of work that fall within our scope.

Connect the website, the shop and the reserved area to the same ERP, with one catalogue

Starting point. A manufacturer or distributor has a website that presents the company and, in many cases, a shop for the public. Trade customers and resellers order by email or phone, often through the agents and each on their own terms; sales documents are sent out one by one. Website, shop and ERP were born at different times and the same catalogue is copied in several places.

Constraints. The ERP remains the source of master data, stock, prices, discounts, orders and documents. The catalogue is one but shows in two ways: to the public with list prices and sales content, to trade customers with their net price, their agreed terms and items the public does not see. Every customer, agent and member of staff sees and does only what falls to them. When data must stay in the company, the internal systems and the database stay on the company network and an identified operator runs the infrastructure.

What we do. We design one platform with several faces, the website, the shop and the reserved area, in the mix the company needs, on a single catalogue base with different views and permissions. A content management system (CMS) serves pages and product sheets. Synchronisation with the ERP works in both directions and is incremental, which means only what has changed is exchanged: master data, stock, price lists and discounts come down; orders go up; confirmations, delivery notes and invoices reach the reserved area from the ERP. The part reachable from the internet sits in a perimeter zone of the network (DMZ) securely connected to the internal systems and talks to them only through the integration layer; no outside system talks to the ERP directly. Installed on the company's own infrastructure (on-prem) or in the cloud, with documented operations either way.

What changes. The public buys in the shop, trade customers order in the reserved area at their own prices and find their documents without asking, agents follow their own customers. The catalogue is updated once. Code, data and documentation remain the company's.

SYSTEMS
ERP, website and B2C shop, B2B reserved area, content management (CMS)
INTEGRATION
integration layer on the company network, API, incremental sync, role-based permissions
DATA
master data, stock, customer price lists and discounts, orders, sales documents

Classify the catalogue to the industry standard without rewriting the product sheets by hand

Starting point. A manufacturer or distributor has a large catalogue, with product sheets written over the years by different people, in free text. Distributors, portals and industry databases ask for every item with the class and technical attributes of the industry standard, for instance ETIM in electrical and HVAC supplies. A large part of the items is not yet classified and doing it by hand costs more than it returns.

Constraints. Master data stays in the ERP or in the product information management system (PIM). A wrong classification is worse than none, so every proposal goes through a person before it leaves. The industry exchange formats come in several versions. Accuracy is measured on real items and agreed before the start.

What we do. We start with a pilot of limited scope on part of the catalogue. We normalise the master data, then a language model installed on the company's own infrastructure (on-prem LLM) or in a European cloud with declared data residency proposes class and attributes from descriptions, technical sheets and images. A person confirms or corrects and every correction improves the next proposals. The result is exported in the formats distributors and industry databases accept. The decision to extend to the whole catalogue is taken on the agreed measure.

What changes. The catalogue can be read by distributors and portals with the standard's class and attributes and searched by technical characteristics. Every new item goes through the same flow. The data pipeline, the model specialisations and the data remain the company's.

SYSTEMS
ERP, product data (PIM), industry database, on-prem LLM or European cloud
INTEGRATION
master data normalisation, assisted classification, human review (HITL), export to industry formats
DATA
product sheets, technical classes and attributes, industry price lists

Read orders and documents with artificial intelligence without data leaving the company

Starting point. Orders, confirmations and technical documents arrive as PDFs, by email or in assorted formats and are copied by hand into the ERP or the catalogue. The company wants to use artificial intelligence to read and classify them. Price lists, customers and documents, however, must not pass through outside services.

Constraints. Data stays inside the company. Every extracted value is checked by a person before it enters the ERP. Accuracy is measured, not assumed. The technical documentation useful for the company's obligations under the EU AI Act is produced together with the system.

What we do. We start with a pilot of limited scope on the company's real documents. Before starting we agree an accuracy measure, for instance the share of documents read without corrections, and the decision to extend or stop is taken on that number. The language models are installed on the company's own infrastructure and connected to the ERP and to the document archive. Every result goes through a person's review before it becomes a record or an action.

What changes. Documents enter the ERP without re-keying, with measured accuracy and a person who decides. Data does not leave the company. The pipeline and the documentation remain the company's.

SYSTEMS
ERP, document archive (DMS), on-prem LLM
INTEGRATION
OCR, semantic search (RAG), human review (HITL)
DATA
orders, confirmations, technical documents

Show every customer their own price and real availability on a catalogue of hundreds of thousands of items

Starting point. A distributor sells a catalogue of hundreds of thousands of items, with variants and compatibility between products, to trade customers. Each customer has their own terms: price lists, multi-level discounts, promotions. Today the customer asks for price and availability by phone or email, a clerk looks the answer up in the ERP and replies, then keys the order in by hand.

Constraints. The ERP remains the source of prices, stock and terms and is not to be replaced. Price rules are complex and change often. Industry price lists and exchange formats arrive in several versions. The catalogue must answer at once, including searches by code, by compatibility and by technical characteristics.

What we do. We analyse the price rules and the data flows of the ERP and reproduce them in a B2B portal built for that volume of items. Synchronisation with the ERP works in both directions and is incremental. Master data, prices and stock flow down to the portal; orders flow up to the ERP without being re-keyed. No outside system talks to the ERP directly. A documented integration layer sits in between.

What changes. The trade customer sees their own net price and real availability across the whole catalogue and orders on their own, at any hour. The ERP receives orders that are already validated. The company measures searches, orders and response times and remains the owner of code, data and documentation.

SYSTEMS
ERP, B2B portal, integration layer
INTEGRATION
API, webhooks, message queues, incremental sync
DATA
master data, customer price lists, stock, orders

Sell high-end products online with an e-commerce store connected to the ERP and to logistics

Starting point. A company that makes or distributes high-end products sells online to consumers. The site has to convey the value of the product, with curated content, quality imagery and fast pages. At the same time it has to work with the company's ERP and logistics. Today catalogue and stock are updated by hand and orders are copied into the ERP.

Constraints. Prices, stock and orders have a single source, the ERP. The catalogue has variants, sizes or configurations and content in several languages. Speed and accessibility affect sales and search rankings. Payments, shipping and returns must talk to carriers and logistics.

What we do. We design the B2C platform around the company and connect it to the ERP and to logistics with documented data flows. The catalogue updates from the ERP or from the system that manages product data (PIM). Stock follows the warehouse. Orders enter the ERP with payment and shipment already attached. The visible part of the site is built for speed and for reading on every device.

What changes. The store sells with data aligned with the ERP and no double entry. The company controls content and catalogue and grows in volume without changing platform. Code, data and documentation remain its own.

SYSTEMS
ERP, B2C store, product data (PIM), logistics
INTEGRATION
API, webhooks, payment gateway, carriers
DATA
catalogue and content, stock, orders, shipments and returns

Replace a B2B platform at end of life without stopping orders

Starting point. The B2B platform in use was built years ago. Its vendor has announced the end of support or its cost has grown beyond the value it returns. It holds customisations nobody documents any more and trade customers use it every day to order. The problem is the platform; the ERP stays as it is.

Constraints. Sales do not stop. Price rules, customer records, order history and ERP integrations must move to the new platform without loss. Upgrading the existing platform instead of replacing it is an alternative to be weighed on equal terms, with its own costs and risks.

What we do. The preliminary analysis takes stock of functions, customisations and integrations and compares the two paths, evolve or replace, on five-year costs and risks. The result is a comparison document with a reasoned recommendation. When replacement is the right choice, the migration proceeds in closed-scope phases, which means scope, deliverables and conditions are written down before each phase: first the integration layer with the ERP, then catalogue and customers, finally the switch of the channels, with both platforms running in parallel for as long as needed. Each phase closes with a review agreed with the company.

What changes. Customers keep ordering without interruption on a platform whose code, data and documentation the company owns, on its own infrastructure or in the cloud as the company chooses, with an identified operator running it. The integration layer stays and, at the next change of ERP, adapts on one side only, without touching the platform.

SYSTEMS
current and new B2B platform, ERP
INTEGRATION
integration layer, phased migration, parallel run
DATA
price rules, customer records, order history

Rewrite the integration when the ERP vendor retires an interface, without changing platform

Starting point. The portal, the e-commerce store or logistics exchange data with the ERP through an interface the ERP vendor has scheduled for retirement on a set date. The integration works, nobody has touched it in years and whoever wrote it is no longer available. Platform and ERP work and stay; what expires is the channel between them.

Constraints. The ERP does not change or changes version with its vendor and on the vendor's schedule. The flows of master data, price lists, stock and orders must continue up to the day of the switch and after it. The new interfaces have limits on the number of calls and access rules that differ from the old ones.

What we do. We draw up an inventory of the flows that depend on the retiring interface and deliver it as a written report the company can use with other suppliers as well. Then we rewrite those flows on the interfaces the vendor supports, in coordination with the vendor's partner, who remains responsible for the ERP. The new integration layer is documented, uses queues and retries to respect the interface limits and is tested in parallel with the old one before the switch.

What changes. The integration is rebuilt once, on supported interfaces, and does not need rebuilding at every ERP upgrade as long as the vendor supports those interfaces. The company holds the documentation of its own flows and no longer depends on whoever wrote them.

SYSTEMS
ERP, portal, e-commerce, logistics
INTEGRATION
supported interfaces (API), queues and retries, parallel run
DATA
master data, price lists, stock, orders