Products and variants
Colour, size and model variants defined in the item master; barcodes, units and measurements managed from one place.
INDUSTRY: RETAIL
Your stores, your warehouse and your online channel on one stock figure.
In retail, the problem is rarely missing data; it is scattered data: store stock reads differently at headquarters, a price change does not reach every channel at the same time, and the numbers never quite reconcile at day-end. SAP Business One holds product, price, stock and sales data in one source, and every channel is fed from it.
What does ERP actually solve in retail?
Businesses that start with a single store hit the same wall when the second and third location open: each store has its own till software, headquarters runs separate accounting, and the online shop has yet another panel. The same product sits in three systems under three different codes, stock figures drift apart during the day, and nobody can say for certain where a returned item ended up.
SAP Business One changes that picture by holding product, price, customer and stock data in a single data model. Store sales, warehouse transfers, supplier goods receipts and online orders all move through the same inventory transactions, and the accounting entries are created alongside them. Instead of merging spreadsheets at day-end, you look at data that was never separated in the first place.
This page addresses the questions retailers ask most often: how the store-to-warehouse stock relationship is built, how prices and campaigns are managed centrally, how till software and e-commerce talk to the ERP, and which reports actually drive decisions.
Processes that map directly to retail operations
The areas of standard SAP Business One most used by retailers; scope is rolled out in stages according to your store count and channel mix.
Multiple warehouses and store stock
Each store and the central warehouse defined as its own location, with live stock visibility and location-based authorization.
Sales and returns flow
Retail sales documents, returns, exchanges and credit notes running in full integration with accounting.
Purchasing and supply
Season- and category-based ordering, goods receipt, supplier invoice matching and cost tracking.
Price lists and discounts
Channel- and store-level price lists, customer-specific prices and volume-based tiered discounts.
Finance and store reconciliation
Cash, card and bank collections tracked per store, with day-end reconciliation.
Store-to-warehouse stock and transfers
Stock accuracy in retail depends as much on transfer discipline as it does on sales. In SAP Business One each store is defined as a separate warehouse; movements from the central warehouse to a store, or between stores, are recorded with inventory transfer documents. The requesting store raises a transfer request, headquarters approves it, and the issue and receipt are traceable in the same document chain.
Goods in transit stay visible too: items that have been issued but not yet received can be tracked in an intermediate warehouse, so a store never sees stock it has not physically received as sellable. Counting runs on the same structure; after a full periodic count or a partial count by category, the difference documents correct stock and cost together.
For item groups that require it (electronics, cosmetics, food), serial or batch tracking is enabled at item level, making it possible to trace which store sold a specific unit and which batch a returned item belongs to.
Pricing and campaign management
Centralised pricing is one of the fastest returns in a retail ERP project. Structures that can be configured with standard SAP Business One:
- Separate price lists per channel and store group
- Linked lists derived from a base list by factor
- Prices and discounts specific to a customer or customer group
- Tiered pricing and discount rules based on quantity
- Period-specific special prices with start and end dates
- Discount control at both line and document level
- Discount authority limited per user
Till, POS and point of sale: what is and isn't standard
It is worth being precise here: SAP Business One is an ERP solution and does not ship with a store checkout front end. The fast sales screen a shop floor needs is covered in one of three ways.
NFKSOFT Store App
Our store front end for sales, returns, stock inquiry and customer transactions, working directly on SAP Business One data.
Integration with your current POS
Keep the till software you use; product, price and stock data flow from the ERP to the POS, sales and collections flow back.
Development for specific rules
Loyalty points, gift vouchers, instalment sales and other mechanics unique to your business, handled as controlled development.
Day-end and till closing
Cash, card and other collection types posted to the ERP per store at day-end, in one reconciled step.
Fiscal device side
Fiscal printer and cash register requirements are evaluated separately, through the interfaces your device provider offers.
In-store stock handling
Category transfers, counting and goods receipt performed with handheld terminals using our warehouse application.
Connecting e-commerce and marketplace channels to the ERP
In multichannel retail, the most expensive mistake is trying to manage the same stock in two places. Your own online shop and your marketplace storefronts should read sellable stock from the ERP; otherwise you sell what you do not have, and cancellation penalties add up fast.
For these integrations we use the official SAP Business One interfaces: the Service Layer and the DI API. The typical flow is this: products, prices and sellable stock go from the ERP to the channel; incoming orders become sales documents in the ERP; shipping and tracking information is written back to the channel; and when a return arrives, stock and accounting are corrected together.
Channel-specific pricing, commissions and shipping costs are part of the design as well. If you want to know which channel is genuinely profitable, those costs have to be recorded at order level. Every transfer is logged, and failed records do not disappear quietly; they collect in a visible queue.
Retail reporting: which question, which report?
Producing reports is easy; producing reports that lead to decisions is not. The figures retail managers follow day to day:
Sales performance by store
Turnover, transaction count, average basket and return rate compared by day, week and month.
Category analysis
Sales, gross margin and stock share by product group, so it is clear which category earns its shelf space.
Stock turnover and ageing
Slow-moving and dead stock identified per store, so markdown and transfer decisions rest on data.
Traffic by day and hour
How sales are distributed through the day, so shift and staff planning follows real footfall.
Channel comparison
Store, e-commerce and marketplace channels side by side on turnover, returns and profitability.
Management dashboards
Web-based dashboards that gather key indicators on one screen, accessible to regional and store managers too.
How a retail project runs
With multiple locations we prefer to prove the setup once and then roll it out, rather than switching every store at the same time.
01
Channel and process discovery
We map your store, warehouse and online processes, your document flow and your exceptions together.
02
Product and stock design
Item and variant structure, warehouse definitions, price lists and the authorization scheme are designed.
03
Pilot store
The setup is validated in one store with real sales, returns, transfers and day-end transactions.
04
Integrations go live
POS, e-commerce and marketplace flows are opened one by one, each handed over in a monitorable state.
05
Rollout and training
Remaining stores are migrated in a controlled way; store and head office teams are trained on their own processes.
Questions retailers ask most
Does SAP Business One replace store POS software?
No. SAP Business One is an ERP solution and does not include a store checkout front end. The need for a fast sales screen is covered either by the NFKSOFT Store App, which works directly on SAP Business One data, or by integrating the POS software you already use. In both cases products, prices and stock stay under central management.
How do we keep store-to-store transfers under control?
Each store is defined as a separate warehouse and movements are made with inventory transfer documents. The requesting store raises a transfer request, headquarters approves, and issue and receipt are traceable in the same chain. Goods in transit are held in an intermediate warehouse so a store never treats stock it has not received as sellable.
Can we run different prices and campaigns per store?
Yes. Separate price lists can be defined per store or store group; linked lists derived from a base list, date-bounded special prices and quantity-based tiers are all standard configuration. Mechanics specific to your business, such as loyalty points or gift vouchers, are handled as custom development.
Can our online shop and marketplace storefronts share the same stock?
Yes, when it is designed properly. Sellable stock is calculated in one place in the ERP and pushed to the channels; orders coming back become sales documents in the ERP. Rules such as stock allocated per channel, reserved quantities and safety margins are decided together during integration design.
If a store loses its internet connection, do sales stop?
In solutions built on central ERP data, connectivity is a critical component, so offline behaviour is a design decision to settle at the start of the project. In the Store App, offline selling and later synchronisation are planned together with a scope and risk assessment. Rather than making a blanket promise, we clarify which option is workable for your store infrastructure.
Related pages
RETAIL
How many stores do you run, and with how many systems?
Tell us about your store, warehouse and online setup; together we will define which processes standard SAP Business One covers and which need an application or an integration.