Skip to main content
GullySystem
E-commerce software ยท Configured implementation

Travel Accessories E-commerce & Inventory Software

The store covers travel accessories: sets built from single units, specification fields, gift capture, light-parcel shipping and returns by grade. The platform is picked in discovery. Chosen marketplaces can share the stock count, on a stated timetable and not instantly.

Product status

Configured implementation on a commerce platform chosen in discovery

The store sits on a commerce platform that you and we select during discovery. No GullySystem product covers travel accessory retail. What can change is limited by the platform.

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 one count of single items, read by every set, pack and channel. A sale anywhere moves the same number. Nobody retypes it that evening.

It covers the storefront, orders and light-parcel handling. Certifying electrical goods and judging the truth of product claims are outside it, and stay with makers and your own adviser.

  • Merchandisers
  • Catalogue editors
  • Packers
  • Support agents
  • Owners
Modules

What is in the system.

Storefront

Filters and comparison on size, type and colour.

Unit and set record

Single items with sets and packs defined over them.

Gift capture

Notes, monograms and box choices saved on the order.

Shipping rules

Weight-band and volume rules for light and bulky parcels.

Returns grading

Resellable, opened and damaged outcomes.

Workflows

How the work runs through it.

Set to parcel

A buyer orders a set. Each piece is drawn from stock, and the packer sees the gift note and the box choice on the pick list.

Return to shelf

A return is graded. The item then goes back on sale, moves to a clearance list or is written off.

Channel sync

One count is shared with chosen marketplaces on a timetable.

Catalogue and product data

What each product record holds.

Facts as fields

Sizes, types, plug standards and lock types are stored as fields.

Sources

Each claim keeps a note of its maker statement.

Colour list

One naming list shared across the store and channels.

Pricing and order rules

How prices and orders are set.

Set prices

A set can have a price of its own or follow its pieces.

Trade prices

Gift and corporate buyers see agreed terms.

Promotions

Offers run by rule between two dates. The store ends each one on time, whether or not anyone is at their desk to switch it off.

Stock and fulfilment

From stock to the doorstep.

Unit count

Every set and pack reads the same count of single items. Nothing is entered twice.

Timed channel updates

Marketplaces receive the count on a stated timetable, and the store holds a small reserve between runs.

Pick lists

Orders grouped for packing with gift notes beside each.

Payments, returns and refunds

Taking money and giving it back.

Payments

Card and UPI checkout for low-value orders. Cash on delivery is added only where you offer it and a carrier collects it.

Refunds

A refund is booked against the order and its grade.

Exchange

A wrong colour or size is swapped without a refund and a second order.

Admin controls and reporting

What the team can see and change.

Roles

Each role sees only what it needs.

Approvals

Large gift orders wait for the owner.

Reports

Sales by accessory and season, returns by reason and carriage per order.

Integrations

What it connects to, and on what terms.

Marketplaces

Linked channel by channel, each after its seller access is checked.

Carriers

Weight-band and volume quotes, trialled per service.

Accounting

A file for your accountant, with a direct link only if scoped.

Deployment

How it is set up and run.

Platform setup

Configured under your own account where the platform allows.

Staged opening

One family goes first.

Customisation boundaries

What can change, and where the edge is.

What can change

Fields, set rules, gift options and page design.

Where the edge is

Product claims and electrical standards stay with makers and your adviser.

Migration and training

Moving over and getting people ready.

Catalogue move

Products and counts are loaded from your spreadsheets or a previous store, then reconciled against your own totals.

Training

A working session for each team, using your own organisers, adapters and locks as the examples, so staff practise on the products they handle every day.

Support scope

What support covers.

Scope

Fault fixes and small catalogue changes, with named contacts.

Outside scope

A new marketplace or a new country is a fresh piece of work.

Subcategory coverage

Where each travel accessories subcategory is covered.

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

  • Travel Organisers

    Covered on this page

    Set stock and colour variants are catalogue configuration within the category solution.

  • Travel Pillows

    Covered on this page

    Volume-based carriage and grading of returns are configuration of the category solution.

  • Travel Adapters

    Its own solution page

    A destination finder, electrical fields and serial-level warranty differ from the plain catalogue of the category solution.

  • Passport Holders

    Covered on this page

    Personalisation fields and proofs sit inside the category solution as order configuration.

  • Travel Locks

    Covered on this page

    Pack variants and marking notes are catalogue configuration within the category solution.

Existing products

What already exists.

No existing GullySystem product covers this requirement on its own. It would be built, as described above.

Services

How it gets built.

For the business side, see Software solutions for travel accessories e-commerce.

Common questions

Questions about this solution.

Is this software available today?

No. Your store is put together after discovery. It is not a finished product.

Can adapters and locks share one catalogue?

Yes. Each product type has its own fields. Adapters can also have a dedicated destination finder.

Will marketplaces see stock the moment it changes?

Not always. Each channel has its own limits, and updates on a timetable are described as such.

Does it verify product claims?

No. It stores claims with their source. Verification stays with your team and the makers.

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.