Skip to main content
GullySystem
Retail

Product Management for Gift shops

Maintain the item definitions used by sales, purchasing and stock.

Inventory Management

Does this function belong in your operation?

Use when several business processes need the same product or service definitions.

An item, service code or variant is added or changed.

Each gift is stored with its occasion, price band, recipient type and supplier. A candle that suits both housewarming and birthday sits under both. Staff find a present for a cousin quickly.

Bring the records the workflow depends on.

  • Item codes
  • Units and variants
  • Pricing and tax references

Outputs to check

  • Controlled item and variant catalogue
  • Unit and classification reference
  • Item-change approval history

Follow the product management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Request the item

    Identify its business use and check for an existing equivalent.

  2. 2. Define attributes

    Set units, variants and required classifications.

  3. 3. Review settings

    Check price, tax and stock-related references with the responsible owners.

  4. 4. Approve use

    Release the item to permitted transactions.

  5. 5. Maintain history

    Control changes and retirement without rewriting earlier documents.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Counter or sales staff

Finds the item by whatever they call it, and sees the rate and what is in stock.

Store and purchase

Adds new items with their units, rates and reorder levels before the first delivery arrives.

Owner

Controls who may change a rate. In most shops that is a very short list.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate item discovered

Review linked transactions before merging or retiring a code.

Unit changes after use

Preserve historical quantities and define any conversion for future entries.

Item discontinued

Restrict new use under the agreed rule while retaining old orders and stock history.

Can this work independently?

The catalogue can exist independently, but sales, purchasing and stock must use its identifiers to share records. Prices and taxes may be maintained in separate controlled settings. Adding an item does not create opening stock or confirm that it is available to sell.

Systems and records it connects with

  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Purchase order management: Authorised supplier commitments and open line balances.
  • Barcodes and labels: Item-code mappings and verified printed-label values.

Configure, test and introduce the workflow.

  • We look at your sheet and counter software. You provide an export, and we report on duplicates and gaps.
  • A coding scheme and categories are proposed. You approve them before anything is loaded. Duplicates are merged with your staff. Each decision is logged for later reference.
  • A sample of items is loaded into a test copy. You check units, rates and tax codes. Billing and stores read from the new list. A short session for each team closes the step.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Item codes are unique.
  • Units remain consistent across transactions.
  • Inactive items follow the agreed transaction rule.
Gift shops

How the business operates.

Gift shops carry thousands of small items that sell in bursts around birthdays, weddings, festivals and the end of the school year. Each burst has its own colours, price points and cut-off dates, and a shop that misses one is left holding boxes that nobody wants until the following year. Gifts are bought in a hurry.

Stock by occasion

Tag each item with the occasions it sells for and the dates they fall on. Slow lines are flagged for markdown before the season closes, and next year’s buying starts from what actually sold.

Personalisation job sheets

A name, a date or a line of text is captured at the counter and sent to the print or engraving bench with a due time. The customer approves the wording before the item is made. The bench never retypes a name.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Counter sales and gift receipts. Scan or search items, add wrapping, take payment in the modes you accept and print a receipt with the price hidden for the recipient. Held bills let one customer shop while another is served.
  • Item list with occasion tags. One record per item holds its supplier, cost, selling price, variants such as colour and size, and the occasions it sells for. Breakable and perishable flags guide how it is handled.
  • Labels and barcodes. Print shelf labels and price tags for new stock, with a code the counter scans. Re-labelling after a markdown is a short job, not a walk round the shop.
  • Stock by shelf and back room. Track pieces on display, in the back room and held for orders. A count of one display bay can be matched to the system without closing the shop.

Operational bottlenecks to check

Seasonal lines have no end date

Heart-shaped boxes, festive lights and graduation frames are bought in bulk, and nothing records when each line should be marked down. What remains turns up in a back room months later, still in its carton, long after anyone could sell it at the full price. Nobody planned that.

Personalised orders live on slips

Names, dates and wording for engraved glass and printed mugs are written on a pad at the counter. A spelling error is found only after the item is made, and the customer will not accept it. Wrong spellings cannot be undone.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Receiving and tagging

    Stock arrives from import suppliers and local makers. Every parcel is opened beside its delivery note, and each piece gets a price label plus tags for birthdays, weddings or festivals.

  2. 2. Sale at the counter

    The item is scanned, a gift receipt is offered and wrapping is added as a charge. If the customer wants a name or date on it, a personalisation job is opened at the same moment.

  3. 3. Approval and bench

    The wording is shown to the customer for approval. The job then reaches the print or engraving bench with its due time, and the sale shows it as pending.

  4. 4. Hamper and parcel packing

    A hamper is built from its parts and its stock is taken from each. Parcels are packed from the order with the card message, and the courier booking is noted.

  5. 5. Cards and consignment

    Gift cards are issued and redeemed against numbered records. Consignment sales are added to each maker’s statement as they happen.

  6. 6. Season close

    At season end the slow lines are marked down and listed for the next buying plan. Makers’ unsold pieces are listed for collection.

Industry reports to connect with

  • Sales and margin by occasion and by item group
  • Personalised jobs due, late and awaiting approval
  • Hampers built, hamper margin and components short
  • Gift card balances, redemptions and expiries

Questions before implementation.

When should gift shops consider product management?

Use when several business processes need the same product or service definitions. An item, service code or variant is added or changed.

What should we bring to the requirements discussion?

Bring anonymised examples of Item codes; Units and variants; Pricing and tax references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Maintain the item definitions used by sales, purchasing and stock. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An item catalogue does not itself manage stock movements or fulfilment.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Item codes are unique. Use this check when reviewing the first working version.

Talk to us

Discuss product management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements