Skip to main content
GullySystem
Healthcare

Order Management for Online pharmacies

Track a confirmed order through fulfilment and billing.

CRM

Does this function belong in your operation?

Use when sales, operations and billing share confirmed orders.

A customer confirms goods or work.

An order from the website, the app or a marketplace opens as one record with its lines and a prescription flag. Agents sort the queue by what needs a pharmacist. Cancelled lines return to shelf stock.

Bring the records the workflow depends on.

  • Order lines
  • Commercial terms
  • Fulfilment rules

Outputs to check

  • Confirmed order and revision record
  • Outstanding fulfilment list
  • Delivered and billed reconciliation

Follow the 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. Capture confirmation

    Record accepted quantities, price and terms.

  2. 2. Check release conditions

    Review credit, approval and any stock or capacity requirements.

  3. 3. Authorise fulfilment

    Pass the confirmed lines to dispatch, production or service delivery.

  4. 4. Record partial progress

    Compare accepted fulfilment evidence with the remaining order balance.

  5. 5. Reconcile and close

    Match billing and approved cancellations before closing the commitment.

Who uses the module, and who approves?

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

Sales executive

Takes the order and confirms the delivery date. Tells the buyer when half has gone.

Storekeeper

Picks against the order. Records short quantity. Closes the line only when it is out of the gate.

Accounts assistant

Bills the dispatched quantity and keeps the advance adjusted against the right order.

Owner

Sees orders pending beyond their promised date, and which customer is waiting longest.

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

Record the supplied portion and retain the balance against its original line.

Customer cancels remaining work

Obtain approval and close only the unfulfilled portion.

Agreed price changes

Version the order and review whether invoices or advances need separate adjustment.

Can this work independently?

Orders can be entered from an accepted customer instruction without CRM. Stock, production, service delivery and invoicing connect through order-line references. Each owns its execution record; an order status should reflect their confirmed outcomes rather than assume delivery from a planned date.

Systems and records it connects with

  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Walk us through an order from call to payment. A note shows the steps and the documents.
  • Decide which changes need approval. A test order can then be taken, with your own staff at the keys. Share orders still pending. The trial import shows quantities dispatched and pending for the storekeeper to check.
  • Sales and the store team practise a part delivery. A note for the counter follows. New orders go through the system from the date you agree. Changes from the opening week are reviewed together. Habits settle quickly.

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.

  • Partial fulfilment leaves correct balances.
  • Term changes follow approval.
  • Billing follows approved quantities.
Online pharmacies

How the business operates.

An online pharmacy has no counter. The prescription arrives as a photo, the pharmacist checks it on a screen, and the medicine leaves in a parcel the patient never sees being packed.

Order queue from every channel

Collect website, app and marketplace baskets into one list with payment status, address and the lines that need a prescription, so staff can spot a duplicate or fraud attempt.

Prescription check by line

Hold the image beside the order and record the pharmacist’s name, time and decision on each medicine, with any substitution approved and any narcotic or opioid line marked.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Storefront and marketplace orders. Collect baskets from your website, app and marketplace listings into one order queue, with payment status, delivery address and a flag on every line that needs a prescription.
  • Prescription upload and verification. Hold each prescription image against its order, and let the pharmacist mark every line accepted, queried or rejected with a name, a time and a typed reason.
  • Restricted item rules. Mark medicines that need a valid prescription, a quantity cap, a cold-storage flag or a no-post rule, so the basket is stopped before payment is taken.
  • Substitution and generic matching. Offer an equivalent generic pack when a brand is out of stock, and record the pharmacist’s approval and the patient’s consent before the substitute reaches the pick list.

Operational bottlenecks to check

Prescription and order live in different tools

The image arrives through chat or upload while the order sits in the storefront, so proving which pharmacist approved which opioid or antibiotic line means searching two places.

Recall notices cannot be answered quickly

A batch is withdrawn. Without a scan at packing, nobody can list every parcel and every patient that received it, so the search is done by hand.

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. Order intake

    A basket arrives from the website, app or marketplace, payment status is recorded, and any line that needs a prescription is flagged on arrival. Nothing skips the queue.

  2. 2. Prescription check

    The pharmacist opens the uploaded image beside the order, accepts, queries or rejects each line, and records any approved substitution together with the patient’s consent.

  3. 3. Picking and batch capture

    Packers receive a pick list sorted by shelf, scan the lot and expiry of each pack, and the system stops any line that is near expiry or blocked.

  4. 4. Packing and dispatch

    The parcel is weighed, labelled and handed to a courier against a manifest, and cold-chain boxes carry a packed-at time with the tracking number sent to the patient. The cold clock starts here.

  5. 5. Delivery, returns and complaints

    Courier status updates the order, and a returned parcel goes to a holding bin where the pharmacist inspects the seal and decides to restock, destroy or return it. Every outcome carries a reason.

  6. 6. Refill and reorder

    From the days supplied on each line a refill date is set, the patient receives a reminder by SMS or messaging app, and one tap repeats the last order.

Industry reports to connect with

  • Orders waiting for pharmacist review, by age
  • Lines rejected or queried, with reason
  • Batches dispatched, by patient and parcel
  • Cold-chain parcels and courier delay

Questions before implementation.

When should online pharmacies consider order management?

Use when sales, operations and billing share confirmed orders. A customer confirms goods or work.

What should we bring to the requirements discussion?

Bring anonymised examples of Order lines; Commercial terms; Fulfilment 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. Track a confirmed order through fulfilment and billing. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Stock, production and carrier connections need agreed scope.

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. Partial fulfilment leaves correct balances. Use this check when reviewing the first working version.

Talk to us

Discuss 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