Industry · Industry & wholesale
REEA builds ordering portals, spare parts shops and field sales apps for Swiss manufacturers and wholesalers. They show customer prices from the ERP, such as SAP or Microsoft Dynamics, and product data from the PIM, and we run them for years.
What we build
Every building block depends on a leading system. That is why our bill of materials always lists the integration next to the service.
| Item | Building block | What it does for your customers | Connected to | Solution |
|---|---|---|---|---|
| 01 | B2B ordering portal and dealer portal | Business customers and dealers order around the clock, with their own terms, approvals and several buyers per company. | ERPCRM | Commerce & ERP integration |
| 02 | Spare parts shop | Find spare parts by item number or machine type, with availability and delivery time from the warehouse. | ERPPIM | Commerce & ERP integration |
| 03 | Customer prices from the ERP | After logging in, each customer sees their prices, discounts and framework agreements, just as they are maintained in the ERP, for example in SAP. | ERP terms | Commerce & ERP integration |
| 04 | Product data from the PIM | Data sheets, attributes and images from a single source, used directly in shop, website and app. | PIMDAM, e.g. Bynder | Commerce & ERP integration |
| 05 | Field sales app | Customer history, prices and orders on a tablet at the customer's site, native for iOS and Android or cross-platform. | ERPCRM | Customer apps |
| 06 | Multilingual website | The corporate website in German, French and English, connected to the shop and product data. | TYPO3PIM | TYPO3 & enterprise websites |
The difference
In wholesale, everything depends on the ERP: item master data, terms, stock, delivery notes and invoices. If the shop stands apart, the back office becomes the interface. When connected, the same order runs through without retyping.
Today with manual handovers
Connected without re-keying
Trigger
Two deadlines are fixed in the calendar. The third trigger is familiar to every head of IT from daily work.
Regular maintenance of SAP ERP 6.0 ends at the end of 2027 and can be extended at extra cost until the end of 2030. If your shop or portal depends on the old SAP, we plan the new interface together with your SAP migration so that sales keep running on changeover day.
Free support for v11 ended at the end of October 2024, and for v12 on 30 April 2026. Anyone who stays pays for Extended Long Term Support (ELTS). We weigh the cost of upgrading to v13 or v14 against ELTS and connect the new website with the shop and product data at the same time.
View the TYPO3 Upgrade CheckThe roadmap is set, but the internal team is at capacity. We supplement it with specialists for ERP interfaces, PHP, .NET and TYPO3, without you having to recruit, and hand over documented code.
Discuss capacityEvidence
Named references from Switzerland and projects of the REEA Group from international markets.
AISymfony shop with SAP integration
Müller + Krempel AG supplies primary packaging for pharma, food and cosmetics. Business customers were to order online, with data directly from SAP.
An online shop based on Symfony, connected to SAP.
Business customers order online. REEA looks after the shop on an ongoing maintenance basis.
AI2customer groups in one shop: business and private customers
ALBIRO AG supplies workwear, protective clothing and safety clothing. One shop was to serve both business and private customers, connected to the SAP backend.
Shop on Magento with Symfony and a web app, connected to SAP.
Both customer groups buy in the same shop. REEA maintains it on an ongoing basis and now also supports a sister company within the group.
Construction company: civil engineering, building construction, conversions, building materials.
View projectYour starting point
There is usually a specific trigger. Choose your situation: we show which solution fits, which project proves it and what the first step looks like.
Order route into the ERP
We build a B2B ordering portal that creates every order, with customer number, terms and line items, directly as a sales order in the ERP. Order confirmation, delivery status and invoice flow back into the portal.
Dealers and business customers
After logging in, each customer sees their prices, discounts and framework agreements from the ERP, plus availability and delivery time. They retrieve status and invoice themselves in the portal.
Shop and website
We calculate the upgrade to TYPO3 v13 or v14 against ELTS and connect the new website to the shop and product data at the same time. If your shop version no longer receives updates, we plan the switch before it becomes urgent.
ERP migration
We plan the new interface together with your ERP consultancy and your migration so that sales keep running on switchover day. The ERP stays with the consultancy; we are responsible for the shop and the interface.
Collaboration
Your ERP consultancy knows your ERP; we know portal, shop and app. The shops of Müller + Krempel AG and ALBIRO AG run with SAP in exactly this way: the consultancy stays responsible for the ERP, and we are responsible for the front end and interface.
AIOperation
For companies with 200 to 1,000 employees, what counts is who will still be looking after the shop in five years. These figures stand behind our answer.
Approach
We map your shop, ERP, PIM and CRM and show where an integration speeds up orders the most.
Ordering processes, roles and screens are created as a clickable draft in Figma, agreed with your internal and field sales teams.
The portal and interfaces are built in parallel and tested with real data from the ERP, together with your ERP consultancy if you wish.
Maintenance, security updates and version changes, hosting in Switzerland or in the EU.
FAQ
Via an interface that creates the order, with customer number, terms and line items, directly as a sales order in the ERP, for example in SAP or Microsoft Dynamics. Order confirmation, delivery status and invoice flow back into the portal in the other direction, so your customers no longer need to ask.
Yes, provided the data is held in the ERP or the PIM. Your customers can then find spare parts by item number or machine type and see availability and delivery time. We clarify how your data is structured in the Integration Check.
Shopware, Magento 2 and Adobe Commerce, Shopify, WooCommerce, PrestaShop and Sylius, and for special processes also a custom build on Symfony. Which system fits depends on your product range, pricing logic and ERP.
Yes. We build all three channels to be multilingual. Product data comes from the PIM for each language, so translations are maintained in one place only.
On request in Switzerland, for example with Infomaniak. Alternatively in Germany or Finland with Hetzner, or on AWS. Our development centre is certified to ISO 27001 for information security.
Integration Check
In the Integration Check we map your shop, ERP, PIM and CRM, show where an integration between order and sales order brings the most benefit, and set priorities. You then receive a written result with a cost estimate.
