The webshop and its product data in one platform
The B2C webshop and the PIM, each with its own admin area, and the B2B ordering platform for dealers are one platform. Together they make a single, integrated solution with everything needed to sell products to end customers and dealers and to serve and support them.
One platform, four parts
-
B2C webshop
For shoppers: a catalogue with categories, filters, search and comparison, a basket, checkout in three steps, payment and a customer profile.
-
Shop admin area
For the shop's staff: order handling, prices and promotions, promo codes, banners, pages, menus and translations.
-
PIM
Where product data becomes content that sells: names and descriptions in several languages, images, the specification and the category the product is found in.
-
PIM admin area
For product managers: data sources and imports, product enrichment, parameters and brands, and a workspace for each shop.
Work
-
Sils
An e-commerce system for a distributor of garden and outdoor power equipment brands: a B2C webshop, PIM and Weborder — a B2B ordering platform for dealers, all synced with the ERP.
Read the case study: Sils sils.lv -
Gigant Mēbeles
A furniture webshop on the same platform — the B2C webshop and the PIM with both admin areas.
gigantmebeles.lv
The shop as the shopper sees it
Everything a shopper sees comes from the two admin areas — product content from the PIM, and prices, promotions and pages from the shop.
-
Catalogue
A category tree, filters by price, brand and the parameters that matter in the category, sorting, search and product comparison.
-
Product page
An image gallery, description and specification, the price with the previous price, availability in stores, delivery time and a leasing calculator.
-
Basket and checkout
Three steps: contacts and delivery, payment method, confirmation. Shoppers buy with an account or as a guest, and as a company too.
-
Payment and delivery
Online banking, card, invoice, cash or leasing. Collection in a store, courier delivery or a parcel locker.
-
Customer profile
Orders and their statuses, purchase documents to download, addresses, and a basket that follows the customer to any device.
-
Several languages
Product content, categories, pages and interface copy are kept per language, each with its own publishing.
Who the platform suits
The platform is for companies that sell goods to end customers or dealers and keep their range, prices and stock in an ERP.
-
The range lives in the ERP
Products, prices and stock reach the shop automatically, and nobody retypes them by hand.
-
There are many products
Descriptions, specifications and images for many products are loaded from a file, and products are mapped to a category from a list of codes.
-
Several shops, markets or languages
Product descriptions and images are maintained once, while each shop has its own category tree, selection of products and warehouses.
-
Marketing without a developer
Shop staff create discounts, promo codes, banners and pages themselves.
A product's path from the ERP to the shop
The ERP knows a product's code, price and stock. A shopper needs more — a clear name, a description in their language, images, a specification and a category. The PIM adds all of that, and the shop receives product data ready-made on a schedule.
Data flows one way, and each piece has one place where it is kept. So the price in the shop always matches the ERP, and a description does not vanish after the next import.
| Kept in | Data | What it gives |
|---|---|---|
| ERP | Product code, price, status and stock per warehouse | Reaches the shop unchanged |
| PIM | Name, address, short and long description in each language | A product the shopper understands |
| PIM | Images and video | The gallery on the product page |
| PIM | Specification: parameters and their values | Filters and the specification table |
| PIM workspace | Category tree, product mapping and warehouses | Each shop has its own catalogue |
| Shop | Discounts, promo codes, collections, banners and pages | Marketing without development |
-
The product's unique code ties it together
A product is recognised in every system by one unique code. The code is chosen to suit the company: it can be an EAN or any other code, including the company's internal one. The import status shows at once the records whose code is not valid, and they can be passed on for correction.
-
A workspace for each shop
One PIM serves several shops. Each has its own category tree, product selection, filters and warehouses — a production and a test shop, for example, or shops in different markets.
The PIM administration
Product managers work in it. They take a product received from the ERP, add everything a shopper needs and decide in which shop and category it appears.
-
Imports and the error list
The PIM reads products from the ERP on a schedule, and every record has an import status. Products with an invalid code can be filtered, exported and passed on for correction.
-
New products at a glance
The start page shows how many new products arrived today, this week and this month, so how many are waiting for descriptions and images.
-
Product card
For each language product managers write the name the shopper sees, the product address and the short and long description. A translation can start from a copy of the main-language text.
-
Specification and parameters
A parameter is defined once and used for every product. It can be numeric, such as weight, or have a list of values, such as colour. The shop builds its specification table from the parameters.
-
Categories and filters
Product managers build the shop category tree in the workspace and reorder categories by dragging them. For each category they choose its parameters and mark which of them are filters in the shop.
-
Images and video
Several images are uploaded at once and ordered by dragging the rows. The first image is the main one. A video is added by its link.
-
Mapping products to categories
A product appears in the shop once it is mapped to a category. Products are mapped one by one or by pasting a list of codes, for example from a supplier file.
-
Specification imports
Key data, specifications and images for a large number of products can be imported from files, which is faster than opening every product card.
-
Warehouses
An ERP usually has more warehouses than the shop needs. The workspace is where you manage which warehouses pass their stock to the shop.
-
Brands and related products
A brand has a name, a link and a logo, and a category can feature its most important brands. Other products can be attached to a product, for example the contents of a set.
Administration: selling and marketing
The shop's staff run promotions and content themselves. Neither a new discount nor a new page needs development.
-
Prices and discounts
Discount rules for products, categories or brands, as a percentage, an amount or a fixed price, for a set period. When the period ends, the price goes back by itself.
-
Lowest price in 30 days
The platform stores each product's price daily and shows the lowest price of the period next to a discount, as consumer protection rules require.
-
Promo codes
A discount on products or on delivery, with a validity period, a usage limit and restrictions by category, brand or product.
-
Collections and banners
Hand-picked product selections for the home page and other pages, and banners with placements and a publishing period.
-
Upselling
Add-on products shown with a product or a category, and an extended warranty the shopper adds in the basket.
Administration: orders and customers
The platform takes an order from the basket to payment, delivery and the invoice, and the staff see what is happening to it all the way.
-
Dashboard
The first page after signing in answers three questions: what state the orders are in, how much has been earned, and what needs doing now.
-
Order card
Status, payment transactions, invoices and other documents, notes and order printouts in one place.
-
Automation
The payment partner's confirmation marks an order as paid, a leasing decision is fetched automatically, and unpaid orders are closed after a set time.
-
Talking to the customer
Emails on order confirmation and status changes, and a message from the order card, for example that the order is ready for collection.
-
Requests and questions
A question about a product, a spare-part order or a request for advice arrives in the admin area with the customer's contacts, photos, a status and staff notes.
-
Reports
A sales report by product and period, income by day and the list of active baskets.
-
Customer accounts
Staff see a customer account, its addresses and orders and can help when the customer gets no confirmation email or made a mistake in the email address.
-
Recording payments
Bank link, card and leasing payments are recognised by the system. A transfer against an invoice or a payment in the shop is recorded by staff on the order card.
Administration: catalogue, content and access
In the same shop administration staff maintain the content of the site and see what has arrived from the PIM and the ERP.
-
Products and stock
Products, prices and stock arrive automatically. On the product card staff see the stock in each warehouse and the price history by day.
-
Warehouses and shops
For each warehouse you set whether its stock counts towards the quantity on sale and whether it is a shop where customers collect orders. Shop addresses, opening hours and map locations are kept in the same place.
-
Pages and blocks
Pages are assembled from ready blocks and arranged in a tree. A page can be copied, published per language and shown to everyone, only to guests or only to signed-in customers.
-
Menus and site elements
Staff change the header, footer and mobile menus, and the details on emails and invoices, in the administration.
-
Articles and booklets
Tips, news and guides with their own categories, and promotional booklets that stop showing when their publishing period ends.
-
Languages, SEO and redirects
Interface texts are translated per language. Page titles and descriptions for search engines, redirects from old addresses and the sitemap are managed in the same place.
-
Users and permissions
Staff access is set by user groups. For each module a group is allowed to view, edit, delete or export.
-
Logs and background tasks
The activity log shows who changed what. Imports, email sending and price recalculation are done by the platform itself on a schedule.
Integrations
The platform does not work alone. Each shop has its own partners; the kinds of integration are the same.
-
ERP
Regular import of products, prices, warehouses and stock.
-
Payments
Bank links, card payments and leasing, each with its own transaction on the order.
-
Delivery
The parcel-locker list from the delivery partner, addresses from the national address register, and delivery prices by order total or by zone.
-
Email
System emails to the customer with the shop's details and copy in each language.
-
Product feeds
Product data files for price-comparison portals and other partners, with a choice of which brands and categories to include.
-
Analytics
Analytics and advertising codes are added in the admin area.
One platform, several installations
Each shop has its own installation of the platform. The core is shared, and the set of modules fits the shop's range and processes — product variants with their own price, delivery prices by zone or shops for several markets, for example.
In both admin areas, staff access is set by user groups, which allow viewing, editing, deleting or exporting module by module.
We prepare the connection to the ERP for each installation separately. A test shop has its own PIM workspace, where category changes can be tried without touching the real shop.
Planning a new webshop or putting your product data in order?
Tell us where you are today, and we will tell you how we would do it.