Skip to main content
GullySystem
Retail

Purchase Order Management for Footwear stores

Record authorised supplier orders and track what remains due.

Inventory Management

Does this function belong in your operation?

Use when purchasing commitments need control before delivery and billing.

The business agrees to purchase goods or services.

A footwear season order commits to a style, colour, width and size run for a particular store or group of outlets. Receiving a carton count does not prove the ordered size mix arrived. Preserve each variant and the supplier’s agreed delivery window so buyers can identify a missing core size before assuming a seasonal range is ready for sale.

Bring the records the workflow depends on.

  • Approved style, colour, width and size-run quantities
  • Destination store and seasonal delivery window
  • Brand or distributor price and commercial terms
  • Variant-receiving checks and purchase authority

Outputs to check

  • Outstanding pairs by style and size variant
  • Late or incomplete seasonal ranges by supplier
  • Receipt and invoice discrepancies requiring review

Follow the purchase order 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. Purchase request

    The requesting team records the item or service, quantity, specification, required date and business reason. Link a stock shortage or project requirement where one exists; a request is not yet permission to commit money.

  2. 2. Manager approval

    The authorised manager checks need, budget and the applicable approval limit. Return incomplete requests for correction and retain the decision. A changed quantity or value must follow the agreed reapproval rule.

  3. 3. Purchase order

    Purchasing selects the approved supplier and records line quantities, rates, tax treatment, delivery location and commercial terms. Issue a numbered PO from the authorised request and retain the version sent to the supplier.

  4. 4. Supplier confirmation

    Record whether the supplier accepts the quantities, price and delivery date. Differences remain proposed changes until purchasing and the required approver agree them; sending the PO is not evidence of supplier acceptance.

  5. 5. Goods receipt

    The receiving team records the delivery in the goods-receipt process against the PO lines. Count accepted, damaged and rejected quantities separately. A partial receipt leaves the balance open; service purchases need the agreed service-acceptance record instead.

  6. 6. Invoice matching

    Accounts payable compares the supplier invoice with the authorised PO and the accepted receipt or service confirmation. Hold price, quantity and additional-charge differences for resolution before posting or approving the bill.

  7. 7. Payment and closure

    The authorised payment process settles the approved invoice. Record its reference, reconcile remaining receipt and billing balances, and close the PO only when fulfilled or formally cancelled. PO closure itself does not execute a bank payment.

Who uses the module, and who approves?

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

Footwear buyer

Approves the size mix and commercial commitment, deciding whether a supplier’s replacement colour or assortment is acceptable.

Store receiver and accounts

Receiving checks pairs and box labels against the ordered variants; accounts use accepted quantities when reviewing the supplier bill.

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.

Partial delivery

Keep missing sizes open even if the supplier delivered the expected number of cartons.

Cancellation

Review the affected seasonal range and existing receipts before cancelling late variants; retain agreed return or credit obligations.

Price change

Obtain the required approval for revised style or assortment costs before amending the commitment.

Invoice mismatch

Hold differences in style, size-run quantity, pair unit or price, supported by the store’s actual receiving count.

Approval limit

Apply the buyer’s authority to additional sizes or replacement styles rather than treating them as cost-free changes to the original order.

Can this work independently?

Purchase orders can run as a controlled register with entered supplier and item data. Goods receipt owns physical acceptance, accounts payable owns invoice matching and posting, and the payment process owns settlement. Connecting those records provides closure evidence; issuing a PO performs none of those later actions.

Systems and records it connects with

  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Vendor management: Approved supplier identities, terms and sensitive-change controls.
  • Your accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • We follow how items are requested, ordered and received. You provide recent orders and supplier lists. A summary note comes back.
  • Rates, credit periods and freight terms are entered for each supplier. The purchase assistant checks them. Stock levels that trigger an order are set item by item. The owner approves the list.
  • New orders are raised on screen while the old method runs. Differences are explained and corrected. Storekeepers receive on phones and accounts match bills. Old order books are closed.

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.

  • Reconcile an ordered size run with pairs received and missing variants.
  • Trace a substitute colour or width to the buyer’s explicit approval.
  • Keep a short seasonal delivery open without making missing pairs available in outlet stock.
Footwear stores

How the business operates.

A shoe is never one item. It is a style in several sizes, two widths and three colours, and each combination is a separate box on a shelf.

Style, size and width grid

Hold each style with its sizes, widths and colours, and see what is on the shelf, in the back room and on order from one screen at the bench. Counts stay per box.

Size-run receiving

Receive a carton against its packing list and check each box label against the shoe it holds, flagging every box that does not match before it reaches the shelf. Short cartons are noted.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Style, size and width grid. Each style is a grid. Sizes, widths and colours sit in rows. The pairs on the shelf, in the back room and on order are shown against every cell, so a gap is visible at a glance.
  • Brand and supplier master. One card per brand and distributor. Price lists, pack sizes, return terms and the styles bought from each are held together, so a buyer can compare how a stiletto line and a loafer line performed.
  • Size-run receiving. Cartons are received against the packing list. Each box is scanned, and mismatched labels, short boxes and pairs with a scuffed vamp are set aside for the supplier with a note.
  • Barcode and price labels. A label per box carries style code, size, colour and retail price, reprinted whenever a price changes so the swing tag and bench scanner agree. A stale ticket is easy to find.

Operational bottlenecks to check

Missing sizes are found at the counter

The grid shows plenty of a style, yet sizes seven and eight are gone. The customer learns this while a fetch from the back room comes back empty. The sale walks out with the customer.

Boxes and shoes do not match

A label says size nine and the shoe inside is a nine and a half. Counts drift from the first week. Nobody notices until a stocktake.

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. Ordering

    Ordering is built from the record. A supplier order is drawn up by style and size run, using last season’s sales by size as the starting point and the rejected widths as a warning.

  2. 2. Receiving

    A carton is opened against its packing list. Staff scan each box and compare the label with the shoe inside, and any mismatch, torn polybag or missing insole card is flagged before shelving.

  3. 3. Shelving and tagging

    Boxes get a barcode and a price. Then each goes to the shelf, the back room or the window display, with shoetrees and tissue paper left where the maker packed them.

  4. 4. Selling

    The cashier scans the box that was fetched. The pair is billed, and the size, width and colour sold come off that outlet’s count while the floor person who fetched it is credited.

  5. 5. Returns and transfers

    Returns carry a reason code. A pair goes back to the shelf, to a cobbler for a resole, or to the supplier, and pairs requested by another outlet are moved on a transfer note.

  6. 6. Season close

    Slow styles, odd pairs and broken size runs are listed together for markdown, and the final stock, including sandals and wellington boots, is carried forward to next season.

Industry reports to connect with

  • Pairs sold by style, size and width
  • Sizes out of stock in active styles
  • Fit returns by reason and style
  • Transfers requested, in transit and received

Questions before implementation.

When should footwear stores consider purchase order management?

Use when purchasing commitments need control before delivery and billing. The business agrees to purchase goods or services.

What should we bring to the requirements discussion?

Bring anonymised examples of Approved style, colour, width and size-run quantities; Destination store and seasonal delivery window; Brand or distributor price and commercial terms; Variant-receiving checks and purchase authority. 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. Record authorised supplier orders and track what remains due. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A purchase order does not confirm supplier acceptance or physical receipt.

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. Reconcile an ordered size run with pairs received and missing variants. Use this check when reviewing the first working version.

Talk to us

Discuss purchase order 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