Custom Ecommerce Development: When the Shop Is Not Standard

Custom ecommerce development builds the parts of a shop that a configured store cannot do: pricing that depends on the customer, products configured before they are priced, quotes and approvals before an order, accounts with credit terms, and integrations with the stock, accounting and logistics systems the business already runs. GBCORP builds these as fixed-price releases on the same engine as its configured e-commerce app, so the cart, checkout, payments and console are already there and the custom work goes where the shop is different.

Standard or custom

Pricing that depends on who is buying

Price lists per customer group, volume breaks, contract prices, currency and tax per market, and promotions that stack by rule. A signed-in customer sees its own prices; a guest sees list prices. The rules live in the backend, not in the page, so they apply identically in the app, the web and the console.

Configurators, quotes and approvals

A product configured step by step with constraints, priced as it is built, and added to the cart with its specification attached. A quote requested instead of a checkout, answered from the console, accepted by the customer and converted into an order. Approval steps for purchases above a limit inside the customer’s own organisation. These are the flows that make a business shop, and they are built as releases.

Integrations with what already runs

Stock from the warehouse system, prices from the accounting system, orders to the logistics system, invoices back. Where a system has an API, it syncs; where it does not, scheduled imports and exports do the job. Each integration is scoped, priced and delivered in the order the business chooses by value.

Checklist before commissioning custom ecommerce

• The rules a standard shop cannot express, written down.
• Customer groups and their price lists.
• Systems the shop must read from and write to, and their access.
• Payment-gateway account in the business’s name, with the methods each market needs.
• Delivery and return rules per market.
• The three numbers to watch: checkout completion, repeat-order rate, average order value.

The numbers to expect

Scoping in one week. The configured foundation live within days; the first custom release in four to eight weeks at a fixed price. Releases every two weeks. Support at a known monthly figure. Customised or more complex functionality is quoted separately before any work starts.

A worked example

A building-materials supplier sells to trade customers at contract prices and to the public at list, quotes large orders, and keeps stock in a warehouse system. On the configured e-commerce foundation, the public shop is live in a week. Three fixed-price releases follow: customer groups with price lists and credit terms, a quote flow answered from the console and converted to orders, and a stock sync with the warehouse system. Trade customers order at their prices in the app and the web; the supplier’s desk stops re-typing quotes; and the finance report reconciles to the gateway.

B2B accounts with several people

A trade customer is an organisation: a buyer who orders, a manager who approves above a limit, an accounts contact who receives invoices. The shop models the organisation, its addresses and its approval rule, and each person signs in with their own role. Order history, statements and credit balance are visible to the organisation, not only to the person who ordered.

Search visibility for a custom shop

A custom shop still needs its products found. Every product has its own address, title, description and structured data with price and availability; category pages are written, not generated lists; feeds for shopping platforms come from the same catalogue. Customer-specific prices are shown after sign-in; list prices are what search engines index.

Multi-market and multilingual

Currency, tax, payment provider, delivery zones and language per market, with right-to-left layouts as a setting. Customer groups and price lists can be per market. One catalogue, several configurations, one console with reports per market and combined.

Reports the business reads

Orders and value by customer group and market. Quotes issued, accepted and converted. Checkout completion and abandonment. Stock-outs and sync errors. Credit balances and overdue accounts. Repeat-order rate. Exports for the accountant. All in the console, live.

Ownership of the shop

Catalogue, customer data, orders and price lists are the business’s, in a dedicated cloud project in its name, exportable at any time. Store and payment accounts are the business’s. Custom releases are the business’s code. No commission on sales, and no credentials retained by GBCORP after a hand-over unless a support contract requires them.

Questions we hear first

Can we keep our current shop and add custom parts?

Where the current shop has an API, yes; often it is cheaper to move to the engine and rebuild the custom parts on it, which the scoping week will say.

Do we need an app as well as the web shop?

The engine produces both from one catalogue; a change shows in both at once.

Is there a commission on sales?

No. Payments settle to your own gateway and the plan is flat.

Who owns the shop?

The business: catalogue, customer data, orders, accounts and, on custom releases, the code.

Where to start

The GBCORP E-commerce and Shopping App is the configured foundation; the GBCORP web development hub sets out the approach. For the standard web shop, read ecommerce website development explained.

GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.