A customer order arrives, the stock displayed does not match the reality of the warehouse, and the sales representative must call the supplier to verify a negotiated price from last month. This type of friction, common in trading, reveals a tool problem before it becomes an organizational issue. The choice of an ERP software suitable for trading determines the fluidity of the entire chain, from purchasing to invoicing.
Electronic invoicing 2026: the ERP criterion that trading can no longer ignore
Since 2026, electronic invoicing has become mandatory for B2B transactions in France. For a trading company, this means that the ERP must be able to connect to a Partner Platform registered by the DGFiP and manage flows via the Public Invoicing Portal.
Have you already looked at the functional sheets of several ERPs without finding this mention? It’s a warning sign. Software that does not natively handle the issuance and receipt of invoices in structured format (Factur-X, for example) will require adding a third-party connector, along with its share of costs and maintenance.
In practice, before any commercial demonstration, ask a simple question to the provider: “Is your solution already connected to a registered Partner Platform?” If the answer is vague, move on to the next one. Choosing an ERP software for trading without verifying this point amounts to investing in a tool that is already behind on regulations.
Industry-specific ERP or general ERP: what trading really demands
A general ERP covers accounting, commercial management, and sometimes inventory. On paper, it ticks the boxes. In practice, trading has needs that these solutions address poorly or not at all.
Pricing conditions and margin management
Trading operates with pricing grids that vary according to the customer, the volume ordered, the period, and the supplier. A general ERP often offers only one pricing level. The result: sales representatives manage their discounts on spreadsheets, alongside the software.
An industry-specific ERP natively covers complex pricing conditions, including cascading discounts, prices by product family, and supplier framework agreements. This is not a comfort; it is the foundation for margin management.
Multi-warehouse and stock traceability
As soon as a trading company manages two or more storage sites, the question of multi-warehouse management becomes structural. A specialized ERP allows for tracking stock movements between warehouses, managing reservations by order, and triggering replenishments by threshold, all from a unified interface.
A general ERP will often require specific development to achieve the same result, which complicates the project and creates technical debt.
Natively configurable vs. custom development: the trap of ERP projects
Many ERP projects in trading derail not because of the software itself, but due to the implementation strategy. The strong trend in recent years has been to limit specific developments to the strict minimum.
Why? Because each heavy customization (a custom-coded batch management module, an atypical validation workflow) makes updates riskier. When the publisher releases a new version, specific developments must be retested, sometimes rewritten. Maintenance costs explode.
The right approach: identify non-negotiable business processes (margin management by family, pricing conditions, multi-warehouse) and ensure they are covered as standard. Everything else can often be handled by configuration or existing connectors.
- Natively covered processes: commercial management, purchasing-sales, multi-warehouse stock, pricing conditions, electronic invoicing
- Processes to connect via API or add-on module: advanced WMS, TMS for transport, EDI with suppliers, B2B e-commerce
- Processes to avoid custom development: anything related to the accounting core or pricing engine, except in very specific documented cases
SaaS or private cloud: what ERP hosting for a trading SME
The SaaS (Software as a Service) model dominates the market. The company pays a monthly subscription, the publisher manages hosting, backups, and updates. For a trading SME, this is often the most pragmatic choice: no server to maintain, automatic updates, and a lower entry cost than a perpetual license.
The private cloud, on the other hand, is suitable for organizations that handle sensitive data or have network latency constraints on their logistics sites. The cost is higher, but control over the infrastructure is total.
One point to check in both cases: data portability. If you change ERP in five years, can you export all your data in a usable format? A publisher that locks the export is a publisher betting on captivity, not on quality.
Concrete selection criteria for a trading ERP
Rather than a long theoretical grid, here are the points to confront during a demonstration:
- Does the software manage conditional discounts and supplier framework agreements without additional configuration?
- Is electronic invoicing operational with a registered Partner Platform?
- Does multi-warehouse stock tracking work in real-time, with order reservation?
- Does the publisher offer native connectors to existing tools (cash register software, B2B e-commerce platform, EDI solution)?
- Are the publisher’s updates compatible with the configurations made, without functional regression?
Each “no” to one of these questions represents a future hidden cost, either in development or in productivity loss.
The ERP market for trading has structured around increasingly specialized solutions. The right ERP is not the one that does everything, but the one that covers your critical processes without unnecessary development. Check regulatory compliance, test the real pricing scenarios of your activity during the demonstration, and demand a data portability clause in the contract. These details are what separate a successful ERP project from a permanent construction site.