Skip to main content
GullySystem
Logistics

Stock Tracking and Alerts for E-commerce fulfilment companies

Show seller-owned physical stock, allocations and holds without confusing them with channel availability or expected returns.

Inventory Management

Does this function belong in your operation?

Use when a fulfilment provider holds seller inventory and needs item or variant availability for accepted orders.

Seller goods are received, allocated, picked, returned, transferred or physically counted.

Online fulfilment needs the available quantity for the correct seller and variant, not a combined product total across clients. Keep physical stock, reservations, holds and expected returns distinct. A cancelled order releases an allocation only after the relevant work is stopped or reversed with evidence. Returned units remain unavailable until inspected and released under the seller’s instruction. Any channel stock update needs a checked mapping and a recorded reconciliation outcome.

Bring the records the workflow depends on.

  • Seller and owner identities with item, variant and unit mappings
  • Count-supported opening quantities and confirmed locations
  • Actual receipt, pick, movement and return references
  • Hold, allocation, disposition and stock-reporting rules

Outputs to check

  • Seller and variant stock by location and availability state
  • Reservation, movement and disposition history
  • Stock-report differences and unresolved count list

Follow the stock tracking and alerts workflow.

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

  1. 1. Confirm the seller stock map

    Link each variant to its physical item and agreed counting unit. Keep identical codes for different sellers separate and retain unresolved mappings before order release.

  2. 2. Record physical receipts

    Compare actual incoming quantities with the seller notice and record the checks performed. Expected shipments and uninspected goods remain distinct from available stock.

  3. 3. Reserve and issue accepted quantities

    Allocate only the relevant seller’s released goods. Record actual picking and handover references without consuming the full order quantity when a line is short.

  4. 4. Handle cancellation and returns

    Release a reservation only after the work is stopped or reversed with evidence. Record actual returned units under a hold until the authorised inspection and disposition outcome is available.

  5. 5. Reconcile and report availability

    Investigate physical counts and movement differences before approved corrections. Preserve the quantity basis and timestamp sent to a seller or channel, plus any failed-update status.

Who uses the module, and who approves?

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

Inventory controller

Maintains seller and variant mappings and reviews count or movement discrepancies.

Receiving and returns custodian

Records actual quantities, condition observations and goods awaiting a disposition decision.

Order controller

Uses released availability and preserves reservations for accepted work.

Seller account coordinator

Obtains the seller’s correction, replenishment or disposition decisions and confirms their recorded scope.

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.

Channel reports more available stock

Compare update timing, held quantities and reservations before correcting the mapped balance. A channel total is not a physical count.

Returned parcel contains fewer items

Record the observed contents and hold unresolved differences; do not restore the expected return quantity automatically.

Seller requests a variant substitution

Obtain the authorised order change and update the allocation explicitly. Similar appearance is not permission to replace an item.

Cancellation follows physical handover

Do not restore stock from the cancellation message. Wait for actual return and the required availability decision.

Can this work independently?

Entered receipts and allocations can support an independent register when every physical event has a reference. Order and return processes provide instructions; the warehouse provides actual quantity evidence. A live channel exchange needs separately validated mapping and access. Seller-owned stock is not provider working capital, and a shortage does not authorise the provider to purchase replacements.

Systems and records it connects with

  • Order management: Accepted lines, allocations and acknowledged cancellation decisions.
  • Warehouse records: Physical receipt, pick, location and handover evidence.
  • Return cases: Observed quantities and authorised restock or continued hold.
  • Seller stock exchange: Supported quantity updates and reconciliation results.

Configure, test and introduce the workflow.

  • Count a seller’s variants and compare the physical mapping with the original channel catalogue.
  • Define availability, allocation and return-release rules with separate decision owners.
  • Test an incomplete return, a cancellation after handover and an old channel update; preserve actual stock and the unresolved differences.

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.

  • Another seller’s goods cannot satisfy the same item code.
  • An expected return never becomes available solely from a carrier event.
  • Cancelled and physically returned quantities have separate evidence.
  • Reported channel balances retain their basis, timing and update outcome.
E-commerce fulfilment companies

How the business operates.

An e-commerce fulfilment company holds seller goods and prepares online orders for carrier handover under the seller’s instructions. The seller’s customer order, the provider’s accepted fulfilment task and each parcel are related but different records. This scope adds channel references, order holds, changed instructions and physical returns to the shared warehouse custody process. It does not assume that the provider owns the products, controls the seller’s checkout or can refund the buyer. Proposed software requirements must show which instruction reached the floor, what actually shipped and which return decisions remain with the seller.

Seller setup and order intake

Agree seller identities, item and variant mappings, packaging instructions and the supported way orders reach operations. Identify who can release a hold, cancel work or approve a changed delivery instruction.

Allocation and pack operations

Use the accepted order version and that seller’s available stock. Keep short picks, split parcels and changed packaging requirements visible before the dispatch handoff.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Seller and channel order references with line and instruction versions
  • Seller-owned item and variant mappings, location and available quantity
  • Reservation and hold reasons with separate release authorities
  • Actual picks, parcel contents, packaging instruction and shipment reference

Operational bottlenecks to check

One order arrives through two routes

A channel export and a manual message can refer to the same sale. Identify the seller, channel and original line before creating more fulfilment work.

Cancellation arrives after a label

The label does not prove collection, but work may already be beyond the point where it can be stopped. Record the request and the actual warehouse or carrier response.

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. Establish the seller’s operating instructions

    Confirm item mappings and actual stock intake, then agree how accepted orders and changes reach the warehouse. Test packing rules and authorised return decisions before using them for live work.

  2. 2. Accept and review the fulfilment request

    Match seller, channel and order-line identity. Retain separate stock, address or seller-review holds and identify which party can clear each reason.

  3. 3. Allocate and prepare parcels

    Reserve available stock belonging to that seller and record actual picks. Keep an unfulfilled balance when only part of the order can proceed; preserve the accepted packaging version.

  4. 4. Book and hand over

    Use approved parcel and carrier details. Record the booking response and physical collection separately, and retain the source of later delivery or failed-attempt events.

  5. 5. Handle changes and returns

    A cancellation request needs acknowledgement of what can still be stopped. Receive returned parcels into a held state, record actual contents and follow the seller’s approved disposition instruction.

  6. 6. Reconcile the seller account

    Match fulfilment work to service charges and unresolved exceptions. Keep buyer refunds, carrier cash collections and any seller remittance separate from the provider’s invoice and bank receipts.

Industry reports to connect with

  • Seller orders awaiting acceptance, hold release or missing item mapping
  • Accepted lines compared with picked, shipped and outstanding quantities
  • Labels awaiting physical handover and carrier events awaiting review
  • Returned units awaiting identification, inspection or seller disposition

Questions before implementation.

When should e-commerce fulfilment companies consider stock tracking and alerts?

Use when a fulfilment provider holds seller inventory and needs item or variant availability for accepted orders. Seller goods are received, allocated, picked, returned, transferred or physically counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Seller and owner identities with item, variant and unit mappings; Count-supported opening quantities and confirmed locations; Actual receipt, pick, movement and return references; Hold, allocation, disposition and stock-reporting rules. 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. Show seller-owned physical stock, allocations and holds without confusing them with channel availability or expected returns. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Recorded stock does not prove product quality, ownership rights or immediate channel synchronisation. Seller replenishment, disposal and buyer refunds remain separately authorised decisions.

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. Another seller’s goods cannot satisfy the same item code. Use this check when reviewing the first working version.

Talk to us

Discuss stock tracking and alerts 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