Skip to main content
GullySystem
Logistics

Business solutions for E-commerce fulfilment companies

Explore software for work such as “Seller order intake and fulfilment-release review”. Review each business function below, including when it fits and what to check before implementation.

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.

Carrier coordination

Record parcel details and the actual booking response through the agreed process. Distinguish label creation, physical collection and later carrier events rather than reporting all three as shipped.

Returns and seller support

Identify returned parcels against the seller and original shipment where possible. Retain observed contents and condition, obtain the applicable disposition instruction and track disputes without making a buyer-refund decision.

Service billing

Reconcile the provider’s storage, pick, pack, shipping or return charges under the actual agreement. Seller sale proceeds and any carrier-held cash require a separate authority and settlement trail.

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
  • Label, carrier acceptance, collection evidence and later event source
  • Return reference, observed quantity, condition and authorised disposition
  • Provider service activity, carrier charge evidence and separate seller settlement references

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.

A return is expected but not received

A return authorisation and carrier event do not establish physical inventory. Keep expected, arrived, inspected and disposition-completed states distinguishable.

Channel stock differs from physical availability

Reserved, held or returned stock can produce misleading totals if treated as available. Record the basis and time of any reported balance and investigate conflicting updates.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  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.

Roles and responsibility boundaries.

Seller account coordinator

Confirms the seller’s authorised contacts and operative packing or return instructions. Keeps a requested change distinct from its acceptance by warehouse or carrier staff.

Order controller

Reconciles incoming channel references and line versions with accepted work. Checks duplicate imports, multiple holds and cancellations that arrive after picking begins.

Pack and dispatch lead

Records actual items, package references and handover evidence. Refers shortages or label changes to their owners before treating a parcel as complete.

Returns reviewer

Records what arrived and the condition observed under the agreed inspection scope. Restock, continued hold or disposal follows the authorised instruction; a returned label alone does not prove the contents.

Accounts reviewer

Separates service charges from merchandise value and seller money. Reviews carrier charge evidence, approved adjustments and actual receipts or remittances.

Reports your managers need.

  • 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
  • Seller service charges with disputed activity and separate money-settlement exceptions

Connections to scope

  • Assess the actual seller order source, warehouse process and carrier account before specifying any connection.
  • Agree identifiers, permission scope, status meanings, duplicate handling and failed-update reconciliation. Manual imports need the same controls. A named marketplace, storefront or carrier is not an installed integration.

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Compare real seller journeys

Select orders with different variants, packaging instructions and seller contacts. Map received order identifiers to the held goods, accepted work and parcel records.

Test conflicting updates

Rehearse a duplicate order, a short pick, multiple holds and cancellation after packing. Check the acknowledgement path and whether an old update can overwrite a newer instruction.

Close the return and accounting loop

Trace an expected return through actual receipt and authorised disposition. Compare service billing, buyer-refund responsibility and any agreed carrier remittance process without merging their balances.

Limitations to settle before implementation

  • This is a provider workflow for seller-owned goods. It overlaps general warehousing; it does not establish a separate ownership or retail-sales business.
  • Seller product claims, buyer refund eligibility and marketplace account decisions remain with their responsible parties. Physical returns handling does not settle those decisions.
  • Cash-on-delivery collection, remittance, cold-chain handling, customs and regulated goods require actual separately reviewed arrangements. No coverage, delivery outcome or peak capacity is assumed.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Seller order intake and fulfilment-release review
  • Client stock allocation and parcel dispatch coordination
  • Returned-parcel receipt and disposition follow-up
  • Seller service billing and shipment exception reconciliation
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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