Run PrestaShop orders with team handling, internal notes, reminders and custom statuses
Advanced Order Fulfilment is a module for PrestaShop stores that gives every order an internal stage, a responsible team and a clear next action alongside its customer-facing order state. Installation adds the workspace to order administration, and a first team with its stages puts the workflow into use within minutes.
As order volume and staff grow, Paid, Shipped or Refunded no longer explains what the company still has to do. An order is waiting for a supplier answer, an address verification, a special packing decision or an agreed call, and the important fact is who owns that action and when it is due. That responsibility needs to remain visible when sales, service, purchasing and shipping all touch the same order. When the hand-off is invisible, the customer becomes the first person to notice the delay.
The module turns those internal steps into a controlled process without changing the commercial state shown to the customer. Each stage carries a translated name and description, colour, responsible team and completion meaning. You arrange the permitted route in a visual workflow editor, recommended next steps guide daily work, and role permissions decide who views, comments, scores, advances or approves an exceptional transition.
Comments stay personal, team-only or shared with authorised colleagues, while personal and team mentions call the right people into the order. Files and pasted screenshots preserve the evidence, assigned reminders return at the due time, and a score from zero to ten sets priority. The central work queue filters by stage, team, score, completion, customer, total and dates, changes the stage of every filtered order in one action, and reports open work and team activity. Browser, sound and staff email alerts bring new assignments and due reminders to the right people.
The result is clear ownership, fewer missed hand-offs, faster treatment of exceptional orders and a reliable record of every decision.
What changes in daily order handling?
Advanced Order Fulfilment adds an internal operations layer to every PrestaShop order. Customer-facing order states remain in place, while the staff receives its own stage, responsible team, next action, conversation, evidence, reminder, score and history beside the order.
- The first section maps the whole system: native order states and internal work remain connected but serve different purposes.
- The workflow section covers ownership: stages, teams, permitted transitions and roles decide what happens next.
- The collaboration section covers context: comments, mentions, attachments and reminders stay with the order.
- The queue section covers management: filters, bulk changes, export, scores and reports turn orders into an operational work list.
- The safety section covers shared work: simultaneous edits, durable history and shop separation protect the current truth.
- The setup section covers control: a quick first workflow expands into detailed notification, privacy, score and file settings.
How does every order receive the right next step and owner?
Internal stages describe the work the team actually performs, such as Waiting for supplier, Address verification, Ready for special packing or Return inspection. Each stage has its own translated name and description, colour, responsible team and completion meaning. The visual editor shows the entire route, including its starting points, final stages and every allowed transition.
Recommended and additional next steps keep the common route close at hand. The module blocks a skipped or disallowed transition, and an authorised exception remains visible in the history. Role rules separately govern viewing, commenting, scoring, reminders, each transition and exceptional changes, so responsibility matches the organisation rather than one broad order permission.
Native PrestaShop order states also route work. Each state points to one responsible team in the relevant shop, and its members receive the assignment when an order enters that state. The internal workflow therefore follows the real work without changing the commercial state shown to the customer.
What stays with the order when work changes hands?
The order panel keeps the current stage, score, elapsed time and complete transition history beside the order details. Each entry records the employee and time, and comments attach to the order as a whole or to the exact decision they explain.
A comment stays personal to its author, belongs to one team, or is shared with authorised colleagues. A mention addresses an employee or an entire team, while people already involved in the order receive the later replies that concern their work. Photos, documents and pasted screenshots join the same conversation after their type and size are verified.
A reminder belongs to the order, a transition or a comment and names one employee or team. It arrives at the due time even when nobody has opened an administration page, then remains visible until completed. A promised callback, supplier answer or refund review therefore returns to the person who owns it.
How does the manager control the entire queue?
The Order Control Center brings together reference, customer, total, native state, internal stage, responsible team, score, comment count, completion and update date. Every column has the appropriate filter, and the filtered result is exported for further operational work.
The same filtered set receives a new internal stage in one bulk action. Permissions and allowed transitions are verified for every order, normal history and notifications are written, and a clear result separates completed changes from orders that need individual attention. A manager handles a whole release, review or exception queue without opening every order.
The dashboard reports open orders, total orders in the workflow, average score, due reminders, active teams and activity for the chosen period. Each employee sees only authorised orders and personal notifications, and team counts reflect the selected shop. The score from zero to ten turns a long queue into a visible priority order.
What happens when several people or shops work at once?
Every transition carries a version. When two employees act on the same loaded order, the first completed change becomes current and the other person receives the winning state before continuing. The comparison and save are one operation, so contradictory decisions never become parallel versions of the same step.
Each shop owns its teams, state assignments, internal stages, history, comments, reminders, notifications, queue and dashboard figures. Employees see only orders and workflow information from shops they are authorised to handle. A native order state has one deterministic responsible team inside each shop.
Retiring a stage or team requires reassignment where active work still refers to it, while completed history remains readable. Removing a comment also removes its stored files. The operational record therefore survives housekeeping and still explains who decided what and when.
How quickly does it start, and how deeply is it configured?
Installation adds the workflow pages and order workspace to the shop administration. A first team, its employees and a few internal stages create a useful process within minutes. Ready defaults activate the order panel, staff notifications, comments, reminders, attachments, scoring and protection against simultaneous changes.
Deeper configuration defines stage languages and colours, team membership, native-state routing, allowed transitions, role rights, completion stages, recommended steps and the visual route. The starting score, maximum attachment size, private-comment default and retention period follow the merchant's own policy, while each shop keeps a separate structure.
New assignments, mentions, replies and due reminders update throughout the administration. The merchant sets the refresh interval and selects browser messages, sound and staff email delivery, while each employee keeps a personal mute preference. The module is therefore quick for a small team to start and detailed enough for several departments, languages and shops.
-
Referencemprorderworkflow
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeBack-office
-
GDPR RelevantNo
-
Business GoalStreamline Operations
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageManage Store
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Adds an internal order workflow layer to PrestaShop so staff can track what needs attention after checkout. It adds team ownership, private order notes, workflow statuses, reminders, attachments and Back Office notifications without replacing PrestaShop's native order states.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v2.2.132026-05-27
- Addedcomplete FR/DE/ES/IT/PL translations
- FixedRepair workflow status admin list
Loading full changelog...
Works Well With Advanced Order Fulfilment
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Measurement
Running Advanced Order Workflow, a back-office team is coordinating the work that happens after an order is placed: custom statuses, assignments, internal comments, reminders and reporting that show who owns the next step. The operational picture is good inside the shop, but managers often still need order data in a spreadsheet for accounting, fulfilment hand-offs or period analysis that lives outside the workflow screen.
Orders CSV List Exporter is a separate tool that covers exactly that gap. It gives staff a controlled download of order data where they choose the period, statuses, paid state, columns, separator and row limit, then pull a dated CSV with practical default columns for order details, documents and totals. It reads whatever the orders already hold; it does not change them.
Used alongside the workflow module, the exporter lets the same team keep coordinating orders in Back Office while handing clean order extracts to finance or partners. One tool organises the people-work, the other carries the numbers out, so reporting no longer means copying grid rows or asking for SQL.
Workflow
A merchant running Advanced Order Workflow is organising post-order tasks across teams: mapping native order states to responsible groups, assigning work, leaving internal comments and tracking reminders so fulfilment never loses an order. That coordination layer answers who does the next step, but it does not by itself manage the physical stock, picking and shipment side of getting goods out the door.
Warehouse Revolution covers that operational layer separately. It is built for merchants who have outgrown flat product quantities and adds warehouses, zones, rack cells, stock movements, reservations, stock takes, purchase orders, receiving, shipments, RMA handling and BOM recipes in Back Office. It handles the warehouse reality while the workflow module handles the task ownership.
Run together, a team gets both halves of fulfilment as complementary tools: the workflow module shows who owns each step and the warehouse module gives the picking, shipping and receiving detail behind it. Orders stop falling between coordination and physical handling, and staff work from a clearer shared view of where each order really stands.
Complement
With Advanced Order Workflow in place, a store already routes order tasks across teams with statuses, assignments, mentions and reminders, so fulfilment and managers see who owns the next step. What that workflow does not provide is a structured place for customer-facing conversations, where the questions, complaints and service history attached to an order live in their own thread rather than scattered emails.
Support Revolution fills that role as a separate help desk inside the shop. Logged-in customers can open tickets, guest ticket creation can be enabled, and staff manage ticket history, customer identity and order-related issues close to the data that matters. It owns the customer dialogue; the workflow module owns the internal task routing.
Side by side, the two cover the full after-sale picture without overlapping: one team uses the workflow tool to move an order forward internally, and uses the help desk to keep the customer informed and the conversation documented. The result is fewer dropped questions and a cleaner record of both the work done and what the customer was told.
Complement
A team using Advanced Order Workflow spends its day in the Back Office order area, assigning tasks, leaving comments and chasing reminders by order reference. When those references are PrestaShop's default opaque strings, staff, support and bookkeeping all struggle to read, quote and match them quickly during that day-to-day coordination.
Custom Order Numbering tackles that separately by replacing random references with structured ones built from dates, counters, shop or customer context, prefixes and suffixes. Its format builder previews patterns before a real counter is consumed, so new orders arrive with readable numbers your people can actually say aloud and search for. It changes the reference an order carries; it does not touch the workflow itself.
Together they make the same orders easier to work with: the workflow module organises the tasks, and the numbering module makes every order in those queues, comments and reminders instantly recognisable. Staff spend less time deciphering references and more time moving orders forward, and bookkeeping matches documents faster.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
- New
