¶ Physical stores - warehouse and in-store pickup
Physical store support in Hummerce lets you run an online store together with a network of physical stores or pickup points from a single panel - each location has its own warehouse and its own delivery method with in-store pickup, while the product catalog, customers and orders stay shared. This is a solution for sales networks that combine online sales with pickup or in-person service at a location, without setting up a separate system for each store.
Last updated: 2026-09-29 (the underlying platform mechanisms - views, warehouses, delivery methods - have existed for a long time; there's no single shared version number for this combination).
¶ Benefits and use cases
- One panel for every location - a shared product catalog, customer base and order handling, without a separate store installation for each location.
- Its own warehouse for every location - stock and availability calculated separately per location, with a reservation priority between warehouses.
- In-store pickup assigned to a location - the customer chooses a delivery method with pickup at a specific location, with its own address, days and pickup hours.
- Pickup-readiness information - a delivery method with in-store pickup can skip the "Sent" status and move straight to a pickup status, with an email reminder after a set number of days if the order isn't picked up.
- A page describing the location - address, hours and location details as a regular static page assigned to a view.
- A sales argument for more expensive or bulky items - the customer can view or pick up the item in person, and the store limits shipping costs.
A physical store in Hummerce is, by standard, a view - the same mechanism that separates a B2B store from a B2C one, or a domestic version from a foreign one. A physical store's view usually has its own main category (a different slice of the catalog, or the same catalog with different availability), its own warehouse and its own delivery methods. Views don't have their own look by themselves - a different look or hidden elements for a physical store's view is template work.
¶ Warehouse and availability per location
- A store can run several warehouses (Assortment -> Warehouses), each with its own stock state: quantity, reservations, minimum balance and the availability time shown on the product page.
- With the "Multi-viewable" warehouses setting enabled, availability in a given view is calculated only from the warehouses assigned to that view - this way, a physical store's warehouse handles availability only for that store (Warehouse).
- When a customer places an order, the store reserves the item in the highest-priority warehouse - if there isn't enough quantity there, it tries the next warehouses by priority. A reservation can also be moved manually to another warehouse from the order.
- The store can show aggregated item availability (as a number or a description) on the item list and product page; this is the sum of availability across all warehouses considered for that view, not a per-store breakdown without extra template customization.
In-store pickup is a regular delivery method flagged in its settings as Own pickup, not a separate module - it's configured like any other delivery method and assigned to selected views, including a specific store's view. Full description of the fields and configuration: Personal pickup. In short, a delivery method with in-store pickup has:
- the location's address details (name, street, city, postal code, country, phone, email) and a description (e.g. address and pickup hours),
- the days of the week and a cutoff time for picking up the order, plus a processing delay in business days,
- the Skip sent status setting - an order with this delivery method skips the general "Sent" status and goes straight to the pickup-ready status,
- a list of allowed payment methods (e.g. excluding cash on pickup for selected delivery methods),
- a separate settings tab with templates for the status-change email title, the reminder for an uncollected order, and the number of days after which the reminder is sent.
¶ The store's page and organizing the sales network
- The location's description (address, hours, directions) is maintained as a static page assigned to the store's view, without a dedicated content type for a "store".
- Closing a store is several separate steps in the panel, not one operation: disabling the assigned warehouse's availability, disabling the static page and disconnecting in-store-pickup delivery methods from that view. With an ERP integration, the warehouse mapping on the integration side also needs updating.
Views, warehouses and delivery methods with in-store pickup are core platform mechanisms - available in all current Hummerce versions. Combining them into a network of physical stores is a way of configuring them, not a separate, versioned module.
- Views - the basis for separating stores within one panel.
- Warehouse with the "Multi-viewable" warehouses setting.
- Personal pickup - a delivery method with the Own pickup setting.
- Static pages - the location description.
- An ERP integration (Comarch ERP XL, Microsoft Dynamics NAV / Navision) - if store stock levels should sync automatically; without an integration, stock is updated in the panel or by import.
- Admin permissions restricted to selected views, if a store's staff should only work on their own location (Admin permissions).
- Requires implementation - it's a configuration of several platform mechanisms, not a single toggle. Typical scope for setting up an additional store:
- creating the store's view (main category, currency and language if different from the default),
- creating the store's warehouse, enabling "Multi-viewable" warehouses, and setting its priority relative to other warehouses,
- creating an in-store-pickup delivery method for that view (address, pickup days and hours, allowed payments),
- a static page with the location description, assigned to the view,
- testing in a test environment and going live.
- Minimum estimated time:
- an additional store with no template changes and no ERP integration - from 8 h,
- integrating the store's stock levels with an ERP - quoted separately.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on:
- the number of stores and how much they differ (prices, assortment, delivery methods),
- template changes (e.g. per-location availability information on the product page, choosing a store at pickup),
- the ERP integration and stock-level synchronization,
- the number of languages and location-description translations,
- the store version - an older version needs an update first (quoted separately).
- The standard has no dedicated store locator or map with live availability - availability is shown as an aggregated value on the product page, based on the warehouse settings.
- Reserving stock for an order with in-store pickup is the same mechanism as for regular shipping - the item is reserved in the highest-priority warehouse, not automatically in the chosen store's warehouse. Warehouse priorities need to be set deliberately so that an order picked up at a store reserves stock from that store's warehouse.
- There's no single "remove store" operation - closing a location is several separate steps in different parts of the panel (warehouse, page, delivery methods).
- Categories aren't assigned to views directly - a different assortment at a store is set through the view's main category, not through a separate category-to-location assignment.
- We do not verify the configuration for legal compliance - opening hours, pickup terms and location information are set by the store.
- A store locator or map with live product availability.
- A "check availability at your nearest store" widget on the product page, independent of the aggregated availability.
- Automatic assignment of a reservation to the chosen store's warehouse at in-store pickup, without manually setting priorities.
- A single operation that closes a store (warehouse, page and delivery methods at once).
Does Hummerce support several physical stores in one panel?
Yes. Each store is a view with its own warehouse and in-store-pickup delivery method, while the product catalog, customers and orders stay shared.
Can each store have its own stock levels?
Yes, after enabling the "Multi-viewable" warehouses setting and assigning a warehouse to the store's view.
Can a customer pick up their order in person at a chosen store?
Yes, through a delivery method flagged as "Own pickup", with an address, pickup days and hours set for that location.
Is a specific store's product availability shown on the product page?
Partially. The store shows aggregated item availability; a separate per-store availability display requires template customization.
How long does setting up an additional store in Hummerce take?
From 8 h without an ERP integration or template changes - the exact time depends on the number of stores and the scope of integration.
Want to see how a network of physical stores could work in your store? Contact the Hummerce team (in Polish).
- Views: Configuration -> Views - creating a store's view, the view's main category (Views).
- Warehouses: Assortment -> Warehouses - list and warehouse details, priority; Configuration -> Settings, Warehouse group: "Multi-viewable" warehouses (no by default).
- Delivery methods: Configuration -> Delivery methods -> Add - the Own pickup field, address details, pickup days and hours, Skip sent status, allowed payments, views.
- In-store pickup settings: Configuration -> Settings, Personal Pickup tab - templates for the status-change email and the reminder, the number of days before a reminder about an uncollected order, the payment symbol blocked at pickup.
- Store page: Content -> Static Pages - a new page assigned to the store's view.
¶ REST API and MCP
- REST API: operations on views, warehouses, delivery methods and static pages in the context of a store's view (REST API).
- MCP (AI assistant - MCP server):
ec2_views_list, ec2_warehouse_list, ec2_warehouse_create, ec2_warehouse_stock_overview, ec2_delivery_methods, ec2_delivery_create, ec2_delivery_update, ec2_pages_list, ec2_pages_get.