Publishing e-commerce - the right title, format and edition

Readers look for an author, the next volume in a series or a particular textbook edition. To buy, they also need information about format, availability and dispatch times. We help publishers and booksellers connect these data in a working sales platform. We organise catalogues, implement Magento and ERP integrations, and handle migrations and performance improvements.

When a publication is listed but hard to find

An author's name appears in several forms. The next volume does not link to the rest of the series. An e-book and a printed edition have separate, unconnected product pages, and reprint information is missing from the product page.

These problems may originate in source data, imports, search or the interface. We examine these dependencies together so that improving one element continues to work after the next catalogue update.

How we help

Metadata that supports navigation

If the same author appears in the database under four name variants and a series exists only as text in a description, replacing the search engine alone will not organise these relationships. It may only index the same disorder faster.

We start by checking data sources, identifying duplicates and defining relationships between creators, series and products. In parallel, we assess search and indexing. An author, character or publisher can then lead to the right titles, and data corrections have a defined way of being maintained through subsequent imports.

Format and edition - especially important for academic publications

The same title may be available as a printed book and an electronic publication. Linking these products should let readers switch formats while retaining information about price, availability and how to access the content.

Academic and specialist publications add edition number, year, academic editor, multiple authors and information about content updates. A new textbook edition may contain changes that matter to buyers, so it should not be treated simply as another format of an older publication.

We reflect these distinctions in the data model, product pages and navigation. Our experience also includes excerpt previews and reader integration. Readers can check whether they are choosing the right version of the content and how they want to use it.

Availability that follows the publishing cycle

An announcement, pre-order, current availability and a pending reprint represent different purchasing options. An announcement can collect interest; a pre-order allows a publication to be ordered with an expected fulfilment date. For reprints, the estimated date and how it is updated in the store are important.

We connect ERP and source-system data with messages and ordering options. We also agree how to handle baskets containing titles available immediately alongside titles arriving later. Buyers receive information about what they are ordering and when fulfilment can be expected.

Large catalogues, migration and performance

With a large catalogue, the number of operations performed for each category and product page matters. We examine database queries, indexing, search engine reads, and application and infrastructure behaviour. This helps us identify the areas with the greatest impact on site performance.

Migrations also require reproducing rules from earlier store versions, preserving necessary historical URLs and adapting data from the existing ERP API to the new platform. Workshops, data mapping and trial migrations help verify these dependencies before launch.

Book subscriptions and bundles

A set of volumes, a publication bundle and a book subscription differ in how they are ordered and fulfilled. The bundle price, availability of its components and rules for handling a delayed title all need to be established.

We have experience supporting book subscriptions and bundles. Customers get a clear presentation of the set, and the team has a defined way to handle these orders, availability changes and subsequent fulfilments.

Experience that supports our work

A catalogue with around 250,000 active products

We migrated a store from a custom platform to Magento 2 with new UX/UI and Hyvä. We organised author data and relationships between print and digital publications while preserving necessary historical URLs. The integration used the client's existing ERP API. The scope covered different formats, pre-orders, reprints, subscriptions and bundles, as well as backend and indexing optimisation.

A store for comic readers and collectors

We designed UX/UI and implemented a Hyvä frontend on a publishing group's shared platform. Navigation used series, creators and characters, while the catalogue included edition information, announcements, pre-orders and reprints. The store gained its own presentation of the range while keeping a shared back office.

An online bookshop with book collections and e-books

We designed UX/UI and implemented a Hyvä frontend for a site offering books, magazines and periodicals for a media and publishing group. It handled both individual orders and subscriptions. The bookshop integrated with ERP, publishing management systems and marketing automation. The platform offered both print and digital versions, including announcements and pre-orders.

How we start

Our first conversation covers the catalogue, data sources and sales cycle. We analyse sample records, relationships between publications, the import process and places where the platform slows down or complicates operations. We then establish the scope of data organisation, functional changes and integrations, plus an implementation or migration plan. We can also take over maintenance and development of an existing store.