Skip to main content
GullySystem
E-Commerce and Digital Commerce

Online stores, dealer portals, subscription commerce and marketplaces built on a business’s own pricing rules

This service covers online stores, wholesale and dealer ordering portals, subscription commerce and multi-vendor marketplaces for businesses that sell to dealers and consumers. They are built on the pricing rules each business already runs. The client owns the system, and catalogue, tiered pricing, checkout, payments, stock, dispatch and returns all live inside it, so no part sits with a vendor. Nothing is rented back.

  • Price list and dealer terms configured as rules
  • Catalogue, stock, orders and dispatch in one console
  • Gateway and courier accounts, data and source code held by the client

Sellers of several kinds use it. Manufacturers take repeat orders from a dealer network. Distributors and wholesalers work on slabs and schemes, retailers bill at a counter and also sell online, and brands ship cash-on-delivery parcels across postcodes with returns to match. Subscription operators run repeat deliveries. Marketplace operators settle money to several sellers. Some projects start from nothing. Others rebuild a store that cannot hold the pricing rules a business runs on, or give a store that shows one price a dealer channel.

The operational challenge

Where online ordering departs from the way a business sells

Price Lists That Do Not Fit a Standard Store

Prices differ by buyer. A business may sell at one rate to a retail customer, another to a dealer on a slab and a third to a buyer on a negotiated contract. Quantity breaks and seasonal schemes sit on top. A standard store shows one price to everyone. Buyers phone for their rate. Discount codes get handed out to keep orders.

Orders Held in Chat Threads

Orders arrive as voice notes, photos of handwritten lists, WhatsApp forwards and calls taken during a site visit, and office staff retype each one into billing. A loose description gets a guessed item code. The wrong pack size ships. Correction needs a return and a credit note.

Stock Sold Through Two Channels

The last piece sells over the counter in the morning and again on the website in the afternoon, because the site works from a stock figure updated days earlier. One buyer gets a cancellation. On a marketplace it dents the seller rating.

Checkout Abandoned at the Payment Step

Phone buyers stop at payment. Common causes are long forms, address fields that clash with the keyboard, no cash-on-delivery option where customers expect one, and a gateway page that reloads on a weak connection. The cart stays unpaid.

Freight Paid in Both Directions

Freight is paid twice. A cash-on-delivery parcel comes back undelivered, and the business still pays the forward leg, the return leg and handling, on top of the sale it did not make. Often nobody records which products, postcodes or discount offers drive the returns, so the same loss repeats in the following month and the one after.

New Stock Waiting for the Website

New stock reaches the shelf first. Online it still waits for photographs, a description, a category, a tax rate, a pack size, a tax code and someone with the admin login to publish it. Advertising points at a stale catalogue.

Order Value Without Order Margin

The invoice figure is easy to read. The margin on that order, after scheme discount, gateway charge, courier bill, return and cost of goods, hides in the billing file, the gateway report and the courier statement. Free-shipping thresholds and discount depth are set blind.

A new theme fixes none of this. The rules for who pays which price, what stock may be promised, how a parcel ships and what happens on return belong inside the system that takes the order.

GullySystem Solution

Commerce built around the catalogue, prices and dispatch route

Work starts from the price list and the item master, then follows the route an order takes from click through payment, pick and pack to the doorstep. The storefront or portal sits on top. Where Shopify or WooCommerce can carry the rules, the platform is customised, and where it cannot, a pricing engine is built and connected to your accounting or counter software.

Pricing Rules Written Into the System

Customer groups, slabs, pack sizes, minimum order quantities, scheme offers, negotiated rates and credit limits are configured as rules the engine applies when a buyer logs in. Each buyer sees their own price. No phone call is needed.

One Stock Figure for Every Channel

Counter billing, the website, the dealer portal and the marketplace listing all read the same availability figure, so a piece sold in one place drops everywhere at once. Stock is reserved at order confirmation. The same piece cannot be sold twice.

One Trail From Order to Doorstep

Payment, invoice, picking, packing, waybill, tracking, delivery and return are all recorded against the same order number, so a parcel query never starts in a chat thread. Staff and customers see the same status.

Operational ROI

What changes when the store follows the business rules

Focus on business value before discussing technology.

Self-Serve

Buyers Place Their Own Orders

Dealers, retailers and repeat customers log in, see their own rates and outstanding position, and place an order at any hour, including after the counter closes. Nobody in the office retypes it.

Availability

Stock Figures Buyers Can Rely On

The availability shown on a product page matches what the warehouse can actually pick, and reserved, backorder and out-of-stock states follow rules set per product. Promises match the shelf.

Checkout

A Checkout That Works on a Phone

Checkout offers short forms, saved addresses, card and wallet options, and cash on delivery only where the business permits it, and the gateway page holds on a weak signal. It fits the buyer’s screen.

Tracking

Parcel Tracking Without Messages to Staff

Confirmation, invoice, dispatch, waybill number and courier updates reach the buyer on an order page and on WhatsApp, so the buyer sees status without messaging the shop. Status messages to staff fall.

Margin

Cost and Margin Recorded per Order

Discount, freight, gateway charge, return and cost of goods are recorded against each order, so shipping thresholds, scheme depth and product promotion can be reviewed against real margin. Margin becomes a report column.

In-House

A Catalogue and Rate Card Staff Can Change

Adding a range, revising a slab, marking an item out of stock or starting a festival scheme is done by the business’s own staff in the admin console. Nobody waits for a developer.

Scope of service

What e-commerce and digital commerce includes

Everything required from operational discovery to production deployment and long-term maintenance.

Commerce Study and Catalogue Planning

The study maps how the business sells today. Customer types, price rules, pack sizes, dispatch routes and returns are written down, giving a catalogue structure, an order flow and a scope for the team to review.

Custom Consumer Storefronts and Apps

Retail storefronts cover browsing, search, product detail and a short checkout, laid out for the phone first, with structured product pages that search engines can read. Android and iOS ordering apps come too. Headless storefronts are covered. Content and commerce are managed apart.

Wholesale, Dealer and Distributor Portals

This is login-based ordering for a sales channel. It covers per-customer price lists, quantity slabs, minimum order quantities, ordering by item code, repeat orders, bulk spreadsheet upload, credit limit checks and the outstanding balance on screen.

Catalogue and Pricing Engine

The engine holds variants, units and pack conversions, tax codes and rates, customer group pricing, quantity breaks, scheme and combo offers and negotiated contract rates. The business’s own staff maintain all of it.

Checkout, Payments and Collections

Checkout takes gateway, bank transfer and wallet payments, part payment and advance, and cash on delivery under eligibility rules the business sets, with a webhook confirming each payment. Approved dealers get credit terms. Payment links cover orders taken offline.

Order Management and Fulfilment Console

One queue holds orders from every channel. It covers confirmation, invoicing, picking and packing lists, partial dispatch, holds and cancellations, and an audit trail records who changed what and when.

Inventory, Warehouse and POS Connections

Stock is reserved at order time across multiple warehouses and store pickup, with low-stock and reorder alerts and synchronisation with counter billing or POS software. Online and offline sales draw on one figure.

Shipping, Courier and Delivery Integration

Postcode serviceability and delivery estimates appear at checkout. Waybills are generated automatically from the courier’s API, pickups are requested, and tracking updates are written back to the order record. A driver view serves own delivery staff.

Returns, Refunds and Replacements

Customers raise return requests with reason codes. The flow runs through approval rules, reverse pickup, a quality check on receipt and a refund or credit note linked to the original invoice. Reports show what comes back and from where.

Subscription and Recurring Commerce

Customers set recurring plans and repeat delivery schedules, and can pause, skip, change quantity or change address from a phone. Collection runs by direct debit or prepaid wallet. Delivery lists go to the route team.

Multi-Vendor Marketplaces

Sellers are onboarded and verified, each with its own catalogue and stock, and commission rules, order splitting across sellers, settlement statements and payout runs sit behind the storefront. A moderation console serves the operator.

Platform Customisation, Migration and Support

Shopify, WooCommerce and Magento stores are customised and extended, and an existing store moves across with its products, customers and order history intact. Maintenance and security updates continue after launch.

Practical applications

Where commerce software is used

Real-world business processes we configure and automate.

Manufacturer Selling Direct Alongside Dealers

A components manufacturer wants to sell to end customers online while its dealers buy from the same company and expect a better rate than the public. One catalogue serves both groups. The public store shows list price. A dealer login shows that dealer’s slab rate, outstanding balance and credit limit before the order is confirmed, and blocks quantities below the minimum. A consumer order can be routed to the nearest dealer holding stock, and that dealer’s margin is recorded on the order.

Distributor Handling Repeat Retail Orders

A packaged-goods distributor supplies grocery and pharmacy counters that reorder the same short list of items each week, by phone, on paper or through a salesman’s visit. A mobile ordering app shows each retailer the last order to repeat, applies the running scheme and respects pack and case conversions. Confirmed orders are grouped by delivery route. The loading list exists before the van leaves.

Consumer Brand Managing Cash on Delivery

A direct-to-consumer brand sends advertising to a store where most buyers choose cash on delivery, and every parcel that comes back undelivered costs freight both ways. The store adds address confirmation before dispatch, cash-on-delivery limits by order value and postcode history, and a prepaid incentive at checkout. Returns are reported by product, postcode and campaign. Marketing and shipping policy follow that report.

Diagnostics Lab Selling Test Packages

A diagnostics chain quotes package rates by phone, and the rate differs by city and by corporate tie-up, so each enquiry becomes a call to the front desk. An online package store publishes each package with its city rate, add-on tests priced as extras, and a home-collection charge by postcode. A corporate rate card sits behind a login. Pre-collection cancellations refund to the original payment.

Subscription Delivery on Daily Routes

A dairy and staples operator runs fixed delivery routes, and every customer account is checked on paper at month end against each driver’s notes. A subscription platform lets customers change quantity, skip a day or pause from a phone, and a route sheet is generated each morning from those current instructions. Billing follows what was delivered. Collection runs through a wallet or direct debit.

Local Marketplace With Several Sellers

An operator building a local marketplace for nearby shops needs sellers to manage their own catalogue and stock while buyers see one cart. Sellers are onboarded and verified. One order splits into separate seller consignments. It tracks commission per category and produces settlement statements and payout runs that the operator can reconcile against each seller’s sales. A console can hold a listing or seller.

Audience fit

Is This Service Right for Your Business?

We partner with established businesses that have outgrown manual processes and want reliable systems.

Manufacturers and Brands With a Dealer Network

Their dealers order by phone, email and WhatsApp. They need per-dealer pricing, credit control and order history without hiring more back-office staff to type orders in from voice notes and spreadsheets.

Distributors and Wholesalers on Repeat Orders

They sell in packs and cases on slabs and schemes, to the same buyers who reorder often, and dispatch is planned by route or territory.

Retailers Selling at a Counter and Online

Showroom billing already runs on a POS. They want an online store or app that sells from the same stock and the same prices, with store pickup as a delivery option.

Subscription and Repeat-Delivery Businesses

Dairy, groceries, meal-box, water, pet supply, service plan and refill businesses need pause, skip, quantity change, route lists and recurring collection in place of a one-time cart. Repeat delivery is the core.

Marketplace and Aggregator Operators

Operators who bring several sellers, clinics, kitchens or service providers onto one platform need commission, settlement and seller quality handled alongside the storefront. The storefront is the easy part.

When a Custom Platform Does Not Fit

A business that sells a few simple products at one price through one courier, with no link to accounting, can use a ready platform. A standard Shopify or WooCommerce theme is enough. Fix a messy item master, rates or photographs before any store is built, because a storefront repairs neither bad data nor enquiries that nobody follows up.

Feature matrix

Enterprise Capabilities in Plain Business Terms

Variants, Units and Pack Sizes

Variants cover size, colour, grade and packing, and piece, box and case conversions follow the units a buyer actually orders in, so one SKU never needs three listings.

Customer Group Pricing

One catalogue, many rate cards. Retail, dealer, distributor and institutional rates sit on one catalogue, with quantity slabs and negotiated rates per account, so nobody keeps a separate price spreadsheet.

Minimum Order and Order Rules

Rules cover minimum quantity, minimum order value and multiples of a pack, and they can restrict product availability by customer group or region.

Credit Limit and Outstanding Checks

Balance and limit are checked before confirmation. Where a person should decide, the order goes on hold for approval instead of being blocked outright, with the approver’s name recorded on the order.

Tax invoicing

Invoices carry tax codes, tax by place of supply, invoice series and credit notes, and an export is ready for the accounts team at filing time.

Stock Reservation and Backorder

Stock is held when an order is confirmed. Each product carries its own backorder, partial dispatch and out-of-stock behaviour, so a made-to-order item and a shelf item follow different rules.

Multi-Warehouse and Store Pickup

Orders allocate from the nearest or preferred location, stock transfers between locations are recorded, and pickup from a showroom is offered as a delivery option.

Postcode serviceability and delivery estimates

Serviceability, charges and expected days show at checkout. Buyers see only what dispatch can do.

Cash on Delivery Controls

Cash on delivery can be allowed by order value, product, postcode or customer history, and a confirmation step runs before any parcel is booked with a courier. Risk is checked before booking.

Returns, Refunds and Credit Notes

Reason codes, approval rules, reverse pickup, quality check and the refund or credit note are all recorded against the original order, so the history stays in one place.

Order Notifications on WhatsApp and SMS

Messages go where customers read them. Order confirmations, dispatch notices, tracking links, delivery updates and payment nudges travel as WhatsApp Business API templates or plain SMS, matching whichever channel the buyer replies on.

Commerce Reporting

The operations console reports sales by product, customer, channel, region and campaign, plus returns, ageing stock and slow movers that show which range is sitting unsold.

Execution roadmap

Our Structured 6-Step Delivery Process

A transparent path from your first conversation to a reliable production release.

  1. 01

    Discovery and Selling Model Study

    Order takers, pricing staff and dispatch staff are interviewed, and customer types, rate structures, schemes, packing, delivery routes and returns are documented from what they actually do. Awkward orders teach the most. The client provides current price lists, a set of recent real orders including awkward ones, and a contact who decides discounts and credit.

  2. 02

    Catalogue, Pricing and Scope Blueprint

    Catalogue structure, pricing rules, order rules and channel scope are written down, with the screens each role will use and the exceptions people handle from memory now. The client provides the item master with codes, units, tax codes and rates, product images and descriptions, and sign-off on the pricing rules. Pricing disputes are settled here, not later.

  3. 03

    Store and Journey Design

    The buyer journey and operations console are designed as clickable screens before development, covering listing, product page, cart, checkout, order queue, dispatch and returns. Clickable screens settle arguments early. The client provides brand assets and two or three nominated reviewers, and their comments are gathered in one round so that design does not circle between opinions.

  4. 04

    Build, Payments and Integrations

    The storefront or portal, the pricing and order engine and the admin console are built, and payments, courier partners, messaging and accounting or POS software are connected. Every account stays in the client’s name. The client provides gateway, courier and WhatsApp accounts in its own business name, test credentials, and access to the system that holds stock and ledgers.

  5. 05

    Trial Orders, Testing and Launch

    The full path is tested with real catalogue data, from order and payment through invoice, pick, pack, waybill, delivery and return, including failed payments and cancellations. A soft launch follows with a few buyers. The client provides staff to place and dispatch genuine trial orders, and a nominated person to sign acceptance once the test list passes.

  6. 06

    Training, Handover and Peak Support

    Handover covers source code, notes on how catalogue and pricing are kept, an operator runbook, and console training for the teams handling catalogue, orders, dispatch and returns. Peak days need a named owner. The client names an owner for each of those four areas and agrees a support arrangement before a large sale or peak period.

Asset handover

What You Receive Upon Project Completion

Everything required to run, maintain, and expand your software without vendor lock-in.

Commerce scope, catalogue structure and pricing rules document
Buyer journey and operations console designs
Storefront, dealer portal or marketplace with source code
Catalogue, variant and pricing engine your staff can maintain
Checkout with payment gateway, wallet and cash-on-delivery rules
Order, dispatch and returns console with role-based access
Courier, messaging and accounting or POS integrations
Product data and existing-store migration where applicable
Production deployment with backups, monitoring and SSL
Staff training, operator runbook and post-launch support arrangement
Connected ecosystem

Connects With the Systems You Already Rely On

We build bridges between your software so you don't have to replace functional existing tools.

Payments and Collections

  • Stripe
  • Adyen
  • PayPal
  • QR collections
  • Recurring direct debits
  • Payment links

Shipping and Logistics

  • ShipStation
  • DHL
  • FedEx
  • UPS
  • Aggregator courier APIs
  • Own delivery fleet

Accounting, ERP and POS

  • QuickBooks and Xero
  • Zoho Books
  • Odoo
  • Counter billing and POS software
  • Custom ERPs

Channels and Marketplaces

  • Amazon seller panel
  • eBay seller panel
  • Google Merchant Centre
  • Meta and Instagram catalogues

Messaging, Analytics and Marketing

  • WhatsApp Business API
  • Transactional SMS and email
  • Support ticket tools
  • Google Analytics and Tag Manager
  • Email and campaign platforms
Engineering foundation

Selected for Reliability, Speed, and Longevity

Technology chosen to match your operational scale and long-term maintainability.

Storefronts and Apps

Next.jsReactReact NativeFlutterProgressive web apps

Commerce Platforms and Backends

ShopifyWooCommerceMagentoMedusaNode.jsNestJSLaravel

Data and Storage

PostgreSQLMySQLRedis

Search and Media

Typesense and ElasticsearchImage optimisation and object storage

Infrastructure and Delivery

AWSDigitalOceanDockerCloudflare CDNUptime and error monitoring
The GullySystem difference

Why Business Owners Choose GullySystem

Work Starts From the Price List

Actual rates, slabs, schemes and exceptions are worked through line by line before design starts, because pricing is the core of the system and not a settings screen.

Stock Figures Before Storefront Styling

A handsome store that promises what the warehouse cannot pick costs more than a plain one that tells the truth. Stock logic comes before styling. The source of the stock figure and the moment it is reserved are settled with the warehouse team before any visual design begins.

A Ready Platform Where One Fits

If Shopify or WooCommerce can carry the rules, that route is recommended and customised, because it leaves less to maintain. A custom build is proposed only when pricing, ordering or fulfilment logic cannot fit a ready platform, even after extensions and plugins have been tried.

Designed for how your buyers pay and receive

The design starts from local buying habits. Wallet payments and cash on delivery, postcode serviceability, undelivered parcels, tax rules by place of supply, and WhatsApp as a customer channel are part of the initial design.

Accounts and Data Held by the Client

Gateway, courier, messaging and cloud accounts are opened in the client’s business name, with GullySystem access scoped and revocable at any time. Customer data stays with the client. Order history and product data export on request.

Support Through Sale Periods

Commerce work continues after launch. Catalogues change, couriers revise their APIs, and peak sale hours go better with a named support arrangement behind the store.

Commercial models

Flexible Engagement Options

Choose an engagement model that matches your operational scope, budget, and timeline.

Fixed-Scope Commerce Build

Defined store, defined scope

For a bounded storefront, dealer portal or marketplace, scoped against an agreed catalogue, pricing rule set and acceptance criteria that both sides sign before build. Cost and timeline are confirmed after scoping.

Channel-by-Channel Rollout

One selling channel at a time

A channel with heavy manual work goes first. Usually that is the dealer portal or the core storefront, and it runs in production before an app, marketplace or subscription channel is added.

Platform Customisation and Migration

Improve or move an existing store

An existing store can be fixed or moved. This is for businesses already on Shopify, WooCommerce or Magento that need custom pricing, integrations, performance work or a move to a platform that fits better.

Managed Commerce Support

Ongoing ownership

Someone stays accountable for the store. Catalogue and campaign support, courier and gateway changes, performance tuning before peak periods, security updates and new features come under a continuing arrangement.

Category-based applications

Find the kind of business you run.

78 product categories and 436 subcategories, each with a page on the business and a page on the software.

Fashion and accessories

Electronics and technology

Beauty and personal care

Home and living

Food, health and nutrition

Baby, kids and family

Sports, outdoor and travel

Pets, garden and outdoor living

Automotive and vehicles

Tools, hardware and building

Books, stationery, hobbies and gifts

Digital goods and learning

Business and industrial supplies

Prefer to search? Browse every category and subcategory.

Ready platform, customisation or custom development

Choosing how to build it.

The right answer depends on how unusual your ordering process is, not on the size of the catalogue.

A ready commerce platform

A hosted or packaged platform suits a business with a standard catalogue, a standard checkout and no unusual ordering rules. It is the quickest route when the platform’s own features already match how you sell, and its running costs and limits are known in advance.

A platform, customised

Where a platform fits most of the need, we configure it and add what it lacks: special pricing, approvals, a dealer login, or a link to your stock system. The limit is what the platform allows its extensions to do, which is checked before we commit to a design.

Custom development

Custom development earns its cost when the ordering process itself is unusual, as in made-to-order goods, negotiated B2B rates or a multi-seller marketplace. It means more design and more to maintain, so we ask what a platform cannot do before we propose it.

An existing GullySystem product

Where a product we already run covers the stock, billing or dealer-order side, it is linked on the category page. The storefront is then configured around it, and only the existing part is described as an existing product.

India and international

Selling in India and in other markets.

Nothing here replaces the India-specific work on this page. These are the things that change when a store sells abroad, and each is confirmed for your markets before it is promised.

Currencies and languages

Showing prices in several currencies is a display setting. Accepting a payment in a currency and settling it to your bank is a separate matter that depends on your payment provider, your bank and your registration. We treat the two separately and confirm the second before it is promised.

Sizes, units and measures

Sizes, weights, voltages and measurement units differ by region. The catalogue can hold a regional size or unit beside the base one, so a shopper sees what they expect and the warehouse still picks one item.

Addresses and delivery rules

Address formats, postcode rules and delivery regions differ by country. Delivery areas, cut-off times and charges are set for each region you serve, and a region you do not serve is shown as such at checkout.

Payment methods

Shoppers pay in different ways in different countries. The methods offered depend on the payment provider you hold an account with and on the markets that provider supports. We confirm what is available for your business before designing the checkout.

Tax and invoices

Tax and invoice rules depend on the jurisdiction, the product and the buyer. We configure what your accountant or adviser specifies, and we do not state a tax rule as fact. Rules for each market are verified with your advisers before launch.

Returns, privacy and product rules

Returns windows, consumer rights, data privacy and product restrictions differ by market. The return policy is set per region, and anything legal about a product or a customer’s data is confirmed with your own adviser for each country.

Cross-border or local fulfilment

Shipping from one warehouse to many countries differs from fulfilling locally in each. The choice changes stock, duties paperwork, carrier integrations and delivery promises, and it is settled in discovery from how you actually ship.

Time zones

Order cut-offs, support hours and scheduled stock updates run on a stated time zone. Where several are involved, each is named, so a promise made in one market is not read in another.

Common questions

Frequently Asked Questions

Straightforward answers to the questions owners ask before getting started.

Should we use a ready platform like Shopify or WooCommerce, or build a custom platform?

It depends on the selling rules. A ready platform suits a manageable catalogue at published prices, with standard shipping and returns and no dealer channel to feed. A custom build fits when pricing varies by customer group, slab, scheme or negotiation, when dealers order against credit limits, or when stock is reserved across counter and warehouse. It also fits when orders split across sellers or vehicles, or when subscription and route delivery logic sits at the centre of the business. Price list and order flow come first. A hybrid is common: a platform storefront serves retail while a custom portal serves the dealer channel and reads the same catalogue.

Can you build a B2B ecommerce platform with dealer pricing, quotations, minimum quantities and credit limits?

Yes. Dealer pricing is core work here. Each buyer is placed in a group with its own rate card, quantity slabs, pack and case multiples, minimum order values and product visibility by group or region. Negotiated rates can be set for specific accounts. A quotation flow lets a buyer request a rate, a salesperson approve or revise it, and the approved quote convert into an order. Credit limit and balance are checked before confirmation. A held order waits for approval, not rejection.

Which payment gateways, courier partners and channels can you integrate?

Most mainstream gateways, couriers and sales channels can be connected, using the business’s own accounts. Payments typically cover Stripe, Adyen, PayPal or a bank gateway, QR collection, recurring direct debits and payment links for orders taken by phone. Delivery covers shipping aggregators such as ShipStation, direct accounts with DHL, FedEx or UPS, and a driver view for own delivery. Amazon and eBay seller panels, Google Merchant Centre and Meta catalogues are also connected, so one catalogue feeds every listing. An unlisted partner’s API is checked in discovery.

Can the store sell from the same stock as our billing software or counter POS?

Yes. Connections cover QuickBooks, Xero, Zoho Books, Odoo, a custom ERP or counter billing software, so stock, item masters and rates move between systems. One system owns each figure. Where the software supports live updates, stock syncs on each movement, and otherwise scheduled syncs run at a frequency matched to how fast the stock moves. Reservation at order confirmation prevents a double sale. Orders and invoices write back to accounts.

Can you migrate our existing store to a new platform?

Yes. Products, variants, images, categories, customers, addresses and order history are moved, and counts and totals are reconciled against the old store before the switch. Search rankings are protected by carrying over the URL structure or mapping old addresses to new ones with permanent redirects. Page titles and structured data are kept. Coupons, reviews and loyalty balances need a decision. The new store runs alongside the old one until sign-off, and the switch is made at a quiet hour when few buyers are browsing.

What drives the cost of a commerce build?

Rule complexity drives cost, not product count. The factors are the complexity of pricing and order rules, the selling channels needed, and whether subscription or multi-vendor settlement is involved. Integrations count, each with a usable API. Product data and images count, as does any history that must be migrated and the share of the console that staff will run. Discovery prices channels and modules as separate lines. Cost is confirmed after scoping.

What decides how long it takes to go live?

Catalogue readiness often matters more than development. The factors are how clean the item master, rates, tax codes and images are, and how quickly gateway and courier accounts and test credentials are issued. Exceptions in pricing rules matter too. So do changes a third party must make at its end, the speed of design review comments and the length of the soft launch. Discovery turns these into a dated schedule. Catalogue preparation can run alongside design and build.

Will the store stay up during a big sale or an advertising push?

Yes, when load planning is done before launch. Catalogue and listing pages are cached, images are resized for the device, the checkout path is kept short, and stock reservation holds when several buyers reach the last unit. Hosting has room to scale and is monitored. A deeper load rehearsal before a large campaign falls under performance engineering, which is scoped separately when the situation calls for it.

What happens if a payment goes through but the order never gets created?

The order is marked paid from the gateway’s server-to-server confirmation against the business’s reference, not from the browser redirect, which a closed tab can lose. A dropped connection leaves no money unmatched. This failure is designed for. A customer pays, the bank confirms, and the app closes before the order row is written, which is exactly the case the webhook exists for. Where a confirmed payment still cannot be matched to an order, it is flagged for review against the gateway settlement report. Heavy sale days put this to the test.

How do you protect customer, order and payment data?

Card details never reach the business’s servers. Payments use the gateway’s hosted or tokenised flow, so card numbers are never stored in the order database or the logs. Traffic runs over encrypted connections. Passwords are stored hashed. Admin access is role-based, and an audit trail records who changed a price, an order or a refund and when each change was made. API keys are kept encrypted outside the code. Security updates apply to platform and server components, backups are automated with a tested restore, and a signed NDA covers confidentiality before discovery begins.

Do we own the platform, the data and the source code?

Yes. The client receives the complete source code and repository access, the database, the catalogue and pricing documentation and the runbook. Gateway, courier, messaging, cloud and domain accounts are created in the client’s business name, so no vendor holds the keys. Data exports at any time. Nothing is licensed back to the client. Nothing depends on GullySystem staying involved. On a platform build, the client keeps its own Shopify or WooCommerce account and all the custom code written on top of it.

Will you train our team and support the store after launch?

Yes. Training covers the people who maintain the catalogue and prices, process and dispatch orders, and handle returns and refunds, one session per role. Each role gets a short written guide. After launch, a support arrangement can cover monitoring, bug fixes, security and platform updates, courier and gateway changes, catalogue and campaign support and performance checks before peak periods. New features follow the selling model.

What do you need from us to get started?

We need four things. First, a clean item master with codes, units, tax rates and current prices, along with product images and descriptions that a buyer can read. Second, written pricing and discount rules. Include exceptions people handle from memory. Third, permission to raise gateway, courier and messaging accounts in the business’s name, with access to the software that holds stock and ledgers. Fourth, one person from operations who can decide business rules such as who gets which price, when cash on delivery is allowed and how a return is approved.

Let’s Connect

Discuss your commerce requirement.

Tell us what you sell, where you sell it and what is hard about it today. We will say plainly whether a ready platform, a customised one or custom development fits, and what each would involve.

  • No obligation consultation
  • Senior engineer reviews your brief
  • Your operational details stay 100% confidential

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements