Skip to main content
GullySystem
E-commerce software · Existing product, extended

Clothing and Apparel E-commerce & Business Management Software

This solution lets a clothing seller list, sell and exchange online from the same style and size record the shop uses. It suits labels, multi-brand retailers and shops adding a website. The storefront is set up for each business. The counter and stock side already exists as a product.

Product status

Existing GullySystem product, with the online storefront configured around it

Behind the counter, GullySystem’s Clothing Store Management Software already runs the shop side, with a size and colour grid per style, counter billing and exchanges. The online store and its order flow are set up around it and scoped for each business.

There is no published price, free trial or live demo for this solution. Scope and cost are settled in a written proposal after discovery.

Purpose and users

The aim is a single stock grid that the counter, the warehouse and the website all read. A sale in one place then changes what the others show, without an evening of corrections.

It covers the storefront, order handling, exchanges and the tie to shop stock. It does not design garments, manage cutting and stitching, or run a factory floor.

  • Merchandisers
  • Warehouse and packing staff
  • Customer care
  • Shop staff
  • Owners and approvers
Modules

What is in the system.

Storefront

A consumer store reading styles, prices and variant stock from the shared record, with an optional trade catalogue for retailers.

Style and size record

Fabric, fit notes, size chart, colours and a stock count for every size, shared with the shop product.

Order management

Orders, payment status, packing and delivery on one order record, with the variant reserved at purchase.

Exchange and returns

A size swap or a return raised against the original bill, with the reason recorded.

Collections and markdown

Launch dates and markdown rules set once and applied to every channel.

Workflows

How the work runs through it.

From style to doorstep

A style is created, sized, photographed, published, ordered, picked by variant and dispatched without retyping its details.

Exchange for another size

A buyer asks for a different size, the original order is read, the return is received and the new size is sent against it.

Season end

Slow styles are selected by collection, marked down on a set date and shown with the new price in the shop and online.

Catalogue and product data

What each product record holds.

Variants

Size and colour are options of one style, each counted separately, so a missing size shows as missing.

Size charts

A chart per brand or garment type is shown on the product page and kept in one place.

Fabric and care

Fibre, care and fit notes are fields the page displays, filled from your own specification.

Pricing and order rules

How prices and orders are set.

Prices and offers

A price per style or per variant, with offers that start and stop on dates you set.

Trade rates

Where retailers order, each sees only the rates agreed with them, and orders can be placed in size runs.

Order limits

Quantities per customer or per variant can be capped when a style is scarce.

Stock and fulfilment

From stock to the doorstep.

One stock grid

The site reads the same grid the shop sells from. Where the connection updates on a schedule, the site holds a variant in reserve in the gap.

Packing check

Tag or barcode scanned against the order before the parcel closes.

Multiple stock points

Stock in a warehouse and in shops can be shown separately, with the dispatch point chosen by rule.

Payments, returns and refunds

Taking money and giving it back.

Payments

Cards, UPI and wallets through your chosen gateway, with cash on delivery handled as its own method.

Returns and exchange

A return reverses or adjusts the original order. A size swap sends the new size against it without a second sale.

Refunds

A refund is raised against the original payment, and the piece returns to stock only after it is checked.

Admin controls and reporting

What the team can see and change.

Roles

Merchandisers, packers, care staff and the owner get screens that match their work.

Approvals

Discounts above a set level and refunds above a limit wait for an approver.

Reports

Stock by style and size, returns by reason, sell-through by collection and online and shop sales together.

Integrations

What it connects to, and on what terms.

Shop product

Reads and writes the style and size record of GullySystem’s Clothing Store Management Software.

Payment gateway

Linked to the gateway you choose, once its test environment and your account have been checked.

Courier services

Rates, labels and tracking for carriers that open their systems, checked carrier by carrier before use.

Messaging

Order and exchange updates by WhatsApp or SMS where the account and templates are approved.

Deployment

How it is set up and run.

Where it runs

Hosting is arranged with you: managed by us, or placed in a cloud account that belongs to your company.

One season at a time

A single collection goes live first, then the remaining catalogue follows.

Customisation boundaries

What can change, and where the edge is.

What can change

Order stages, return reasons, size charts, markdown rules and page layouts are set around how your business sells.

Where the edge is

Garment design, cutting, stitching and factory scheduling are outside this solution.

Migration and training

Moving over and getting people ready.

Bringing the data over

Styles, sizes, colours and counts come across from the system or sheet in use today, then are reconciled to your own totals.

Training

Merchandisers, packers and care staff practise on your own styles in short sessions.

Support scope

What support covers.

Scope

Fixes, minor changes and day-to-day help are set out in the proposal, along with response hours and named contacts.

Outside scope

A new marketplace, another country or a bigger change is quoted separately.

Subcategory coverage

Where each clothing & apparel subcategory is covered.

Each subcategory is either covered by this solution or has a page of its own where its software requirements differ.

  • Women’s Clothing

    Covered on this page

    Variants, size charts and exchanges are what the category solution covers, and fit data sits in the same record.

  • Men’s Clothing

    Covered on this page

    Two-measure sizes and bundle offers fit the style and variant record the category solution uses.

  • Children’s Clothing

    Covered on this page

    Age guides, sets and gift options sit in the same catalogue and order flow the category solution provides.

  • Activewear

    Covered on this page

    Attributes, sets and fit feedback fit the category catalogue, so no separate system is needed.

  • Underwear

    Covered on this page

    Size grids, packs and returns rules are handled by the category catalogue and order flow, with different settings.

  • Swimwear

    Covered on this page

    Scheduled launches and split sizing are settings of the category catalogue and need no separate system.

  • Outerwear

    Covered on this page

    Seasonal planning, attribute fields and alteration holds are all supported by the category catalogue and order flow.

  • Ethnic Wear

    Its own solution page

    Measurement capture, stitching jobs and one-of-a-kind stock differ from ready-to-wear and need their own data and flows.

Common questions

Questions about this solution.

Can the store be installed as it comes?

No. Only the shop’s back office is a product today. The website and its links are set up for each business after discovery.

What does it cost, and can we try it?

We publish no price list and offer no trial. A written proposal sets scope and cost once we have seen your catalogue.

Does it include stitching or production?

Not on its own. Cutting and stitching are separate work. A made-to-measure flow is a different system and is assessed on its own.

Can it work with software other than your shop product?

It depends on what that software can share. We look at what it can export or expose first, then report what can and cannot be linked.

Requirement discussion

Talk through your commerce requirement.

Describe what you sell, where you sell it and what is slowing you down. An engineer will reply within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Only your name, contact details and a short description are required.

Your details stay private. Privacy policyProtected by reCAPTCHA.