Merchandise management system for SMEs: Functions, costs & selection

An merchandise management system consolidates purchasing, warehousing, and sales into a single database. It shows at any time which items are available, which orders are open, and which documents belong to a given order.

For many small and medium-sized enterprises (SMEs), the purchase of such a system becomes a pressing issue when Excel spreadsheets and separate programs no longer work together: inventory levels are inaccurate, prices are inconsistent, and delivery commitments cannot be reliably met. The real challenge rarely lies in the software itself, but rather in data quality, interfaces, and processes.

This article explains which functions an merchandise management system for SMEs truly needs, how it differs from an ERP system, what costs and project duration you should expect, and how to objectively compare providers in a demo. The focus is on Austrian SMEs in the retail, e-commerce, manufacturing, and service sectors.

Table of contents

• What is an merchandise management system?
• merchandise management system or ERP: What's the difference?
• What functions does an merchandise management system need for SMEs?
• Industry check: Retail, e-commerce, manufacturing, and services
• Selection criteria: Cloud or on-premise, interfaces, usability
• How much does an merchandise management system cost for SMEs?
• Step-by-step implementation: from requirements to go-live
• Conclusion
• FAQ about merchandise management systems

What is an merchandise management system?

An merchandise management system often abbreviated as ERP (enterprise resource planning) or business management software, centrally manages a company's flow of goods: from purchasing and warehousing to sales, delivery, and invoicing. Item master data, inventory levels, prices, and documents are stored in a single database instead of being scattered across multiple files and programs.

The practical benefit arises from data reuse: An item is entered once and is subsequently available for purchase orders, goods receipts, quotations, delivery notes, and invoices. This eliminates duplicate data entry, and the figures in purchasing, warehousing, and sales are consistent.

An ERP system typically provides:

• a central database for items, customers, suppliers, and prices
• traceable goods movements for receipts, transfers, and issues
• a seamless document chain from quotation to invoice
• reliable inventory levels as a basis for planning and delivery commitments
• reports on sales, inventory coverage, and open transactions

How to tell that Excel is no longer enough

Excel is manageable as long as only a few people are using it and the number of items remains manageable. It becomes problematic as soon as multiple employees make changes simultaneously.

Typical warning signs include:

• Stock levels in the list regularly differ from the actual inventory;
• the same items or customers exist multiple times with different spellings;
• prices and discounts are researched anew for each offer;
• the status of an order can only be clarified by asking;
• inventory counts are lengthy and reveal significant discrepancies;
• reports are created manually and quickly become outdated.

If several of these points apply, the problem is usually not a lack of diligence, but rather the lack of a common data source.

Which results are realistic

An enterprise resource planning (ERP) system accelerates processes primarily through standardization. Order processing becomes faster because items, prices, availability, and shipping data are consistently available, and documents are generated directly from the process.

Realistically, this translates to less manual data entry, fewer queries between sales and the warehouse, and significantly shorter inventory counts. However, it's unrealistic to expect that unclear responsibilities or inconsistent pricing logic will be resolved solely through software. An ERP system maps processes; it doesn't replace them.

Merchandise management system or ERP: What is the difference?

An merchandise management system covers the flow of goods and the document chain. An ERP system (Enterprise Resource Planning, i.e., company-wide software for resource planning) expands this core functionality to include other areas such as financial accounting, controlling, human resources, and planning.

For SMEs, this distinction is crucial because it determines the scope, costs, project duration, and organizational effort. A system that is too large complicates simple processes, while one that is too small will later hinder growth.

In practice, the lines are blurred. Many modern systems for SMEs start as merchandise management systems and can be expanded modularly to include accounting or project functions. This phased approach reduces risk and initial costs: you first stabilize your core processes and only expand when the need actually arises.

If the boundaries are unclear within your own company, it's worth taking a structured look at your processes and interfaces before comparing providers. FIGULI CONSULTING supports small and medium-sized enterprises in selecting, implementing, and operating merchandise management and IT infrastructure, determining which system scope best suits your operations. This way, you avoid paying for modules that no one uses in daily practice.

And what about blue office?

blue office is modular – it can be used as both an merchandise management system and an ERP system, and you only pay for the features you need.

Clarify your requirements with FIGULI.

What functions does an enterprise resource planning (ERP) system need for SMEs?

It is not the length of the function list that determines the success of the project, but rather the fit with your processes and data. Prioritization into must-have, target- and optional-requirements has proven successful. This means the comparison remains objective and the introduction does not overwhelm the organization or budget.

Essential, must have functions: the basis for daily operation

Essential functions ensure smooth daily operations. These include a clean item master with units, packaging sizes, and—where necessary—variant logic, as well as merchandise management for each storage location.

In purchasing, you need supplier management, order processing, goods receipt, and invoice verification. In sales, the entire document chain, from quotation to order and delivery note to invoice and credit note, must be seamless, including pricing and terms logic.

Should have functions: faster noticeable benefits

Target functions improve efficiency and data quality most quickly. Barcode scanning and mobile warehouse processes significantly reduce typing errors and accelerate goods receipt, relocation, order picking, and inventory because data is recorded directly at the shelf instead of later at a desk.

The article on mobile data capture in the warehouse demonstrates how this translates into practical benefits. It makes sense to first implement automations that save time on a daily basis—not those that appear most impressive in a demo.

Optional features: important as soon as requirements increase

These functions become relevant when regulatory or sales requirements increase. Batch and serial numbers are crucial for traceability, warranty processing, and quality management, for example, in the food industry, medical devices, or electronics.

A variant matrix is ​​worthwhile as soon as a product exists in many variations, such as size and color—otherwise, the master data multiplies. Consider whether these features are needed now or only in two to three years. Both are legitimate decisions; they should simply be made thoughtfully.

Industry check: Trade, e-commerce, craftsmen, production and services

The best feature list is of little use if the system doesn't fit the business model. Pricing logics, data volumes, and warehousing processes vary considerably depending on the industry.

Trade and wholesale

Speed ​​and terms are paramount here. Customer-specific pricing, tiered discounts, promotional periods, and minimum order quantities must be reliably managed.

Reservations and backorder management are equally important: If an item is not fully available, the system must accurately reflect the partial delivery and automatically track the backorder. Otherwise, you'll end up with precisely the manual wish lists you were trying to eliminate.

E-commerce with shop integration

In online retail, data quality is crucial. Product data, variants, images, and attributes must be consistent because they are directly visible in the shop.

The key is up-to-date inventory across all channels: If you sell through your online shop, marketplace, and physical store, every sale must be immediately reflected in the shared inventory. Otherwise, you risk overselling and cancellations. In the demo, clearly explain how often inventory synchronization occurs and what happens in the event of an interface failure.

Craftsmen

For craftsmen, mobile access and time tracking are essential, in addition to order processing and documentation. They typically require pre- and post-calculation for labor and materials.

When using applications for CAD, measurement, or tendering, interfaces for import and export (Datanorm, ÖNORM A 2063, GAEB) are crucial.

Production

Bills of materials are crucial in production. The system should be able to track material consumption, intermediate storage, completion reports, and feedback from production.

Depending on the product, scrap, rework, and serial numbers may also be relevant. It's essential to realistically assess whether merchandise management with manufacturing functions is sufficient or whether true production planning is necessary—the latter being significantly more complex to implement and maintain.

Service

Service companies such as agencies, consultancies, or craft businesses have little need for storage, but they do require project management, time tracking, and billing. A traditional, retail-oriented system is often unsuitable for them. This article on ERP for service providers discusses which functions are more relevant.

Selection criteria: Cloud or on-premise, interfaces, usability

In addition to the functions, technical and organizational criteria determine the long-term benefits: operating model, interface quality, usability, rights concept and support.

Cloud or On-Premise

• Cloud means the software runs in the provider's data center and you access it via a browser.
• On-premise means operation on your own company's servers.

For most SMEs without their own IT department, cloud computing is the more pragmatic approach. On-premises solutions remain viable if machines, point-of-sale systems, or legacy systems are tightly integrated locally or if offline operation is required.

Regardless of the model, it's crucial to establish binding backup and recovery procedures. Even with cloud software, the question of how quickly you can resume operations after a failure or accidental deletion is a valid one. The article on cloud strategy describes what a sound policy decision on this should look like.

If personal data is processed—which is always the case with customer data — you need a data processing agreement with the provider in accordance with the GDPR. The Austrian Data Protection Authority summarizes the obligations of data controllers.

Check interfaces, don't just query them

Interfaces are often the critical success factor. For Austrian SMEs, the transfer of data to accounting and tax advisors is particularly important, in practice usually to BMD or RZL, or via a standardized export interface.

Typically relevant interfaces include:

• Accounting and tax advisors, such as BMD or RZL
• Online shops and marketplaces
• Point-of-sale systems with mandatory electronic cash registers
• Shipping service providers for labels and shipment tracking
• E-invoicing, especially for public sector contracts

Don't just query interfaces, test them with real test data: Is the field mapping correct? Are tax codes transferred correctly? What happens in case of an error, and where do you see it? An interface that only exists in the data sheet will cost weeks later. The Austrian Federal Economic Chamber offers guidance on procuring suitable e-invoicing software.

Evaluate usability in everyday life

Usability isn't revealed in sales presentations, but in everyday use: clear interfaces, fast search, sensible default values, and easily understandable statuses.

Therefore, test with the people who will be using it daily – one person each from purchasing, warehousing, and sales. Have them click through a typical process themselves, instead of just having it demonstrated. How many clicks does a standard order require? Where does it get bogged down? This observation reveals more than any list of features.

How much does an enterprise resource planning (ERP) system cost for SMEs?

The costs are comprised of several components. Experience shows that the greatest expenses arise not from the license, but from data quality and integrations.

How long the introduction will take

The duration depends on process maturity, data quality, and the scope of integration. A streamlined project with standard processes and few interfaces can go live in just a few weeks. Multiple warehouses, shop integration, and custom pricing logic significantly extend the timeframe.

Plan for a stabilization phase after go-live. Unforeseen issues will arise in the first few weeks. Those who plan for this period will experience it as normal rather than a crisis. A detailed description of the project phases can be found in the article on ERP implementation.

Avoid hidden costs

Hidden costs almost always arise from data issues: duplicates, inconsistent units, missing EAN codes, unclear storage locations, and inconsistent pricing logic.

This can be avoided through early data analysis. Review your master data before inviting vendors. Often, this is the most tedious but most effective preliminary work of the entire project—and it's beneficial regardless of the system you choose.

In Austria, SMEs can also access subsidized consulting through the KMU.DIGITAL program for digitization projects. It's worth exploring this option before starting a project.

Step-by-step introduction: from requirements to go-live

A successful implementation is achieved through clear phases, binding responsibilities, and rigorous testing. SMEs benefit from a pragmatic approach: first stabilize core processes, then expand.

1. Define goals and scope, assign responsibilities
2. Document requirements as concrete use cases
3. Conduct vendor demos with identical test cases
4. Run a pilot project with real data and clear acceptance criteria
5. Go live with enhanced support readiness
6. Stabilize and gradually optimize

Migration from Excel and legacy systems

The migration begins with a data inventory: Which files exist, which fields are reliable, and which source should be considered authoritative in case of doubt?

This is followed by data cleansing: removing duplicates, defining article number logic, standardizing units, and structuring storage locations. Finally, perform a test import with samples before migrating the complete dataset.

Demo checklist for comparing providers

Have all vendors demonstrate the same processes. Only then will the results be comparable:

• Order through invoice, including partial deliveries and backorders
• Goods receipt with storage in a specific warehouse location
• Reservation logic for low stock levels
• Returns with credit notes
• Pricing with tiered pricing and customer-specific conditions
• Transfer to accounting with real test data
• An evaluation of open transactions or delivery capability

Typical mistakes in selection and implementation

Projects most often fail due to excessive scope, unclear responsibilities, and a selection of functions that lacks process relevance.

Equally critical: Data migration starts too late, interfaces are never tested with real data, and training is relegated to the last week before go-live. Binding acceptance criteria, a test plan with deadlines, and early user involvement reliably prevent these issues.

For SMEs that cannot manage selection and implementation on their own, FIGULI CONSULTING provides support throughout the entire process: from process analysis and realistic interface testing to operation. With blue office, FIGULI relies on an industry-independent solution tailored to small and medium-sized enterprises that can be set up and trained relatively quickly – a significant cost factor, as a large portion of the project budget typically goes toward implementation and training.

View blue office for ERP

Conclusion

An merchandise management system provides the foundation for managing purchasing, warehousing, and sales using a consistent data basis. Four key elements are crucial for success: a clear distinction between merchandise management and ERP, a feature list prioritized as essential, and desirable, robustly tested interfaces to accounting, the online shop, and shipping, and an implementation plan that takes data migration and testing seriously.

The most important lever lies before the software decision: those who understand their processes and master data make faster choices, negotiate more effectively, and implement more smoothly. Skipping this step will cost them later in the project.

FIGULI CONSULTING supports Austrian SMEs in structuring requirements, realistically evaluating interfaces, and planning implementation to ensure stable operations.

Discuss your selection with FIGULI CONSULTING

FAQ about the merchandise management system

What is an merchandise management system?

An merchandise management system centrally controls a company's flow of goods: purchasing, warehousing, sales, delivery, and invoicing. Item, inventory, and document data are stored in a common database, ensuring all departments work with the same figures and eliminating duplicate data entry.

How do merchandise management systems and ERP systems differ?

An merchandise management system focuses on the flow of goods and the document chain. An ERP system expands this core functionality to include areas such as financial accounting, controlling, human resources, and planning. For SMEs, a phased approach is often beneficial: first, stabilize the merchandise management system, and later expand it modularly.

What are the minimum functions an SME needs?

Essential features include an item master, merchandise management for each storage location, purchasing with goods receipt, sales with a complete document chain from quotation to invoice, inventory counting, and standard reports. Barcode support, as well as roles and permissions, provide additional benefits early on.

Cloud or on-premise: Which is better for an SME?

For SMEs without their own IT department, the cloud is usually more practical because operation and updates are handled by the provider. On-premises solutions remain viable if point-of-sale systems, machinery, or legacy systems are tightly integrated locally. A stable internet connection is a prerequisite for cloud computing.

Which interfaces are important in Austria?

The key interface is the transfer to accounting, usually to BMD or RZL, or via a standardized export interface. Depending on the business model, online shops, point-of-sale systems, shipping providers, and e-invoicing may also be involved. Test each interface beforehand with real test data.

How much does an ERP system cost?

In addition to the license or subscription, there are costs for implementation, data migration, interfaces, training, and ongoing support. The greatest effort is usually required for data quality and integrations, not the software itself. A reliable estimate is only possible after clarifying processes and interfaces.

How long does implementation take?

Streamlined projects with standard processes and few interfaces can go live in a few weeks. Multiple warehouses, shop integrations, or custom pricing logic significantly extend the implementation time. Plan for a few additional weeks of stabilization after the go-live.

When does an merchandise management system make sense?

An merchandise management system makes sense when stock levels, prices, orders, or delivery commitments can no longer be reliably managed using Excel and individual solutions. Typical signs include duplicate master data, manual document chains, unclear order statuses, lengthy inventory counts, and error-prone interfaces between the warehouse, sales, and accounting departments.