Where the price starts

A customer with several branches picks which one it is ordering for with one click. Each branch has its own price list, delivery address and e-mail addresses for confirmations. For chains with twenty or more shops this is the difference between a portal that gets used and one that gets bypassed.

When a customer does call, the sales rep steps in as them, sees their prices and cart and orders for them. The order carries a mark of who entered it, so it is known later. The phone stays; the retyping goes.

Minimum quantities and packs, a full-pack discount, sale by the metre or roll, order approval before it goes to the ERP, promotional prices per item or category. Every rule that lives in a sales rep's head today gets mapped into the system.

A separate view for warehouse staff: a printable pick list with item photos and the customer's note, statuses new, in progress and sent, courier and tracking number, and a record of who sent what and when.

Invitations to every customer from the ERP, grouped by e-mail and branch, a welcome message with instructions and support for your customers in the first weeks. A portal is worth as many customers as log in.

A sales rep at the customer orders from a phone, with the same prices and stock, even without signal. The warehouse scans barcodes instead of retyping codes.

SKUs from the ERP are grouped into products where the customer picks an option with one click, and the order carries the exact code. Grouping survives every ERP sync and works alongside the import you already have.

Interface, categories and legal pages in the new language with hreflang, so Google knows whom to show what. Product descriptions are translated by you or a translator; we put them in place.

Business customers log in and see their prices and discounts from the ERP on the same webshop; private customers see retail prices. One catalogue, two kinds of customer.

Labels and pickup requests for DPD, GLS or the post from the order itself, tracking number to the customer by e-mail, delivery status in the admin.

A second storefront on the same catalogue and stock. An item is edited once, both channels show the same figures, orders from both land in the same ERP.

The whole site in English or German with hreflang and its own sitemap, so each version ranks for its own market.

Projects or products as their own pages with photographs, data and filters, which the owner adds on their own. For Sprega that is 22 projects from Frankfurt to Budva.

Your locations, quarries, branches or sites on a map in your colours, with a panel per point and clustering of points that are too close.

Your product scanned from photographs and turned in the browser, with a texture from the real surface, lighter on a phone so it runs smoothly. For stone, wood, ceramics, anything sold by its surface. Plus finishes shown on the surface.

A pass through the plant, quarry or production assembled from frames and driven by scroll, with markers that lead to projects or products.

Every address on the old site redirected to the new one, domain and e-mail moved without interruption, with DNS records written in advance. Google loses nothing.

Shopify Markets with currencies and languages per country, prices and shipping per market, VAT per country. That is how Bamboccini ships to fifteen countries.

Klaviyo flows for abandoned carts, new customers and after the order, with your design and copy, sent automatically.

Meta and Google campaigns for the first thirty days, with a Conversions API that measures even with cookies blocked. The ad budget goes to the platform directly.

Fiskalizator from the Shopify App Store: every paid order becomes a fiscalized receipt with JIR and ZKI, the customer gets a PDF. Six months at no charge with a store we build.

A rule Shopify lacks: price by quantity, shipping by zone, a checkout field, a connection to a warehouse or ERP. See the category below.

Stock and prices from your system into Shopify, orders back with the exact code, a queue when the system does not respond.

A screen in the Shopify admin where you change the rules yourself, with a record of who changed what and a report of what the app did.

If you want to sell the app to other stores: subscription billing through Shopify, documentation, passing Shopify's review, user support.

SKUs from the ERP into products with an option picker, which survives every sync and works alongside the import you already have.

Items, prices and stock into the webshop, orders back without duplicates, a queue when the ERP is down. See also the connection category below.

Your own settings in the WordPress admin, who may do what, records and a report of what the plugin did.

Automated tests that warn before a new WooCommerce version breaks something.

A catalogue of models with their own sizes, borders and rules, or a size by the square metre the customer enters themselves.

Logo colours are replaced automatically by the nearest colour of your material, the palette shows real photographs of the material, and the customer is told which shades are too close.

Price by item code from your ERP instead of a price list in the app, so it changes in one place.

Login through an existing wholesale portal, wholesale prices and payment by quote instead of by card.

Designs, orders, production jobs and a record of every change with the person's name.

A job sheet in the form your manufacturer uses, with the same fields and names, plus a browser add-on that fills their form in by itself.

Business customers from the ERP log in to the webshop and see their own prices and discounts.

The customer sees the order status in the webshop and downloads delivery notes and invoices as PDF.

An enquiry from the webshop becomes a quote in the ERP that the sales rep finishes and the customer accepts in the webshop.

A customer with several branches picks the delivery address they are ordering for.

One ERP to several webshops, or several warehouses with their own stock, from the same connection.

The app works in the warehouse or in the field without a network, and data syncs when the connection returns, with conflict resolution.

A barcode scanner using the camera instead of expensive terminals, photos attached to a job, the customer's signature on screen.

Owner, sales rep and warehouse see different screens from the same data, with permissions per role.

A database and API we set up, with an admin in the browser. When you later introduce an ERP, the data connects without rebuilding the app.