ERP for Bookstores — software for retail bookshops, publishers and online booksellers
The DACH book trade runs on extreme range depth (over a million live ISBNs in the VLB), thin 20–35 per cent margins, statutory fixed-book pricing (Buchpreisbindung) and a publisher-conditions structure that no off-the-shelf retail ERP understands. An ERP for bookstores has to combine VLB master-data sync, wholesale ordering through Libri, KNV-Zeitfracht and Umbreit, automated returns (Remission) and ISBN-driven stock control — while keeping the POS, web shop and Genialokal marketplace on one inventory. Generic ERPs without a VLB connector are practically unworkable above a single till.
Requirements
The Verzeichnis lieferbarer Bücher (VLB), operated by MVB, is the central German-language book master-data service. Bookseller ERPs pull daily VLB updates and reconcile ISBN, title, author, publisher, fixed price and availability against the local catalogue. Without that feed, manual maintenance against 10,000+ new titles per year is impossible. Beyond master data, the system has to model statutory fixed-book pricing under the Buchpreisbindungsgesetz (BuchPrG) — including the narrow legal exceptions (used, damaged, library sales). VAT rules also need care: print books carry the reduced 7 per cent rate in Germany, e-books moved to 7 per cent in 2019. Bookstores also expect tight POS integration with barcode scanning, customer-account management for subscription series, and a multi-channel inventory view that syncs shop-floor stock with the web shop and marketplaces such as booklooker, ZVAB or Genialokal in near-real time.
Mandatory functions
The core mandatory feature set covers VLB ingestion, electronic wholesale ordering and statutory returns. Bookstores order through the three German wholesalers — Libri, KNV-Zeitfracht and Umbreit — or directly with publishers, each with its own discount scale, payment terms and minimum-order rules. A good bookstore ERP picks the cheapest channel per title and quantity, holds publisher conditions matrices, and sends EDI orders in BWA or ONIX-for-Books formats. Remission is the second non-negotiable workflow: unsold titles return to the publisher within a defined window. The ERP must produce a Remissionsschein, post the stock movement, track the credit note and respect publisher-specific deadlines. Customers also expect an ISBN scanner workflow at the till, subscription management for series customers, a clean DATEV interface and POS-Kasse integration that satisfies KassenSichV / TSE.
Vendor landscape
The market is dominated by specialised DACH vendors with deep wholesaler links. Buchhandlungs-EDV (buch-shop.com), Lehmanns CMS for academic booksellers, OPP as a cloud option with strong POS integration, scriptum for mid-market Sortimenter and BuchSoft for small shops all bring native VLB and Barsortiment connectors. For publishers and self-distributing imprints, ditAS, BIANCA, BUCH-IT, Klopotek, P3 Verlag and booxbuch dominate title-management and royalty accounting. Generalists such as Microsoft Dynamics 365 Business Central appear in publishing houses that operate their own warehouse, almost always with a partner-built book-trade add-on. Pure NetSuite or SAP rollouts are confined to the largest publisher groups. For independent bookshops, the realistic choice is between a specialist branch system and a hybrid where the till runs on a dedicated bookseller front end while the back-office sits on a modern ERP with VLB middleware.
Trends and outlook
Three trends shape current selection projects. First, omnichannel: independent bookshops are using Genialokal and their own Shopify or Shopware front ends to compete with Amazon, which forces real-time inventory across till, web and marketplaces. Second, e-books and print-on-demand: tolino, BookBeat and audio platforms create digital revenue streams that have to flow into the same revenue ledger as print, and POD-on-demand fulfilment via libreka! or BoD changes the procurement model. Third, second-hand and antiquarian trade: ZVAB, AbeBooks and booklooker integration is becoming standard for shops that mix new books with curated used stock, which requires unique-item handling alongside the standard ISBN-keyed catalogue. Modern Auswahlprojekte in 2026 should test all three on shortlists.
Related Topics
Frequently Asked Questions
Can a generic retail ERP handle a bookstore?
Not really. The VLB feed, the Barsortiment EDI links, statutory fixed-book pricing under BuchPrG and the standard Remission workflow are all so specific that a generic retail ERP forces parallel spreadsheets and manual entry within weeks. Above a single till and roughly 5,000 active titles, the operating cost of fighting the generic system overtakes a specialist branch ERP quickly.
How does fixed-book pricing (Buchpreisbindung) affect the ERP?
The publisher-set retail price is binding in Germany and Austria for new German-language books. The ERP must enforce that price at the till and in the web shop, reject manual discounts on in-scope titles and allow only the narrow statutory exceptions (used, damaged, library, foreign-language). Audit-grade logging of price overrides is expected by the Steuerberater and useful in any later book-trade association review.
How are returns (Remission) handled?
Books are returnable to the publisher within a window typically of 6–12 months, subject to the publisher's conditions. A bookstore ERP runs a Remissionsvorschlag that picks candidate titles, prints the Remissionsschein, posts the outbound stock movement and tracks the inbound credit note from the publisher or Barsortimenter. Missing the deadline turns returnable stock into permanently owned inventory, so deadline alerts are a hard requirement.
Which option fits a bookstore with a strong online channel?
Either a specialist branch ERP with a strong multi-channel module (OPP, scriptum) or a hybrid stack — specialist till plus a generalist back-office such as Microsoft Dynamics 365 Business Central with a book-trade add-on, plus Shopify or Shopware on the front end. The hybrid path gives more flexibility for marketplace expansion (Genialokal, AbeBooks, ZVAB) but requires careful middleware and inventory synchronisation work.