An MTO order for two linen armchairs in Quality Check, assigned to Joana Pinto, due 04/11/2026, with the note Natural linen, fabric reference L-204, the buttons QC Approved - Complete, QC Failed - Rework and Cancel, and an activity log from its creation to Send to QC.
The MTO Orders listing: an oak bookshelf In Production for Rui Teixeira, linen armchairs in Quality Check for Joana Pinto, and an ash bench In Production for Carlos Mendes whose due date, 23/10/2026, is red, each row with its transition buttons.
A shipment form whose items read Oak dining table, MTO-2026-00140, Completed, with a check mark, and Linen armchair, MTO-2026-00141, Waiting for Materials, with an empty circle.
Production Analytics for four weeks: 11 MTO orders, 4 completed, 75% on time, 9.1% canceled, 83.3% first pass in quality check, 18.2% waited for materials, average queue, production and lead times, throughput, and each maker's totals and lead time.

Commerce Make-to-Order is for Drupal Commerce stores that make what they sell after it is ordered: furniture, handmade goods, made-to-measure clothing, print on demand. Each order item becomes a production (MTO) order that the workshop takes from the queue through production and quality check to completion, with a maker, a priority and a due date. The Commerce order moves on once its production is done, and its shipments show which MTO order goes in each one.

Features

  • ๐Ÿ›’ A production order for every order item. One MTO order per order item, for the line's quantity, created when the Commerce order reaches the state you choose, by hand, or with drush mto:create. Numbers come from a Commerce number pattern, MTO-2026-00001 by default.
  • โš™๏ธ Your production workflow. Eight states out of the box (Draft, Queued, Waiting for Materials, In Production, Quality Check, Rework, Completed, Canceled), or any State Machine workflow per MTO order type. Transitions are buttons on the listing and on the MTO order, each with an optional note; canceling takes its own permission. Every transition, assignment and note lands in a timeline on the MTO order, and team notes can be copied to the Commerce order's log with an email to the shop.
  • โฐ Makers, priorities and due dates. Each MTO order has the maker it is assigned to, a priority from Low to Urgent, a due date and an estimated completion date set a number of days after creation. A due date that has passed turns red, and the listing filters and its dashboard count the MTO orders past theirs.
  • ๐Ÿ“Š Production analytics. Queue, production and lead times, completion on time against due dates, quality check first pass and rework, waits for materials, the time spent in each state, and each maker's numbers, for any date range. Each MTO order shows its own times too.
  • ๐Ÿ›’ The Commerce order follows production. When every MTO order of a type reaches the state you choose, the Commerce order moves to the state you choose. Order states you mark as hold, such as a customer who asked to wait, are never left automatically: a note is logged on the order instead.
  • ๐Ÿ“ฆ Shipments that know their production orders. With Commerce Shipping, each MTO order points at the shipment that carries its order item, and follows it when items are split, merged or moved. A second MTO order on the same order item, for a replacement or an exchange, goes with the second shipment that carries it. Code that creates a shipment for a given MTO order, such as the return shipment of a repair, can pin the MTO order to it, so it stays there whatever shipped before. The shipment form shows, next to each line, the MTO order that goes in that shipment and whether it is ready.
  • ๐Ÿ”Œ An event for site code. Before an MTO order created from a Commerce order is saved, an event lets site code set its fields, such as a maker or a due date of its own.

An MTO order for two linen armchairs in Quality Check, assigned to Joana Pinto, due 04/11/2026, with the note Natural linen, fabric reference L-204, the buttons QC Approved - Complete, QC Failed - Rework and Cancel, and an activity log from its creation to Send to QC.

Quick start

composer require drupal/commerce_make_to_order
drush en commerce_make_to_order
  1. At Commerce > Configuration > MTO order types, edit Default.
  2. Under Auto-creation settings, tick Automatically create MTO orders from commerce orders, choose in Trigger on state the state your orders reach once they are paid or placed, and save.
  3. Place an order and move it to that state.
  4. Commerce > Make-to-Order now lists one MTO order per order item, in Draft, with Add to Queue and Cancel buttons.

 an oak bookshelf In Production for Rui Teixeira, linen armchairs in Quality Check for Joana Pinto, and an ash bench In Production for Carlos Mendes whose due date, 23/10/2026, is red, each row with its transition buttons.

The production team's listing, one row per MTO order, grouped by Commerce order.

A shipment form whose items read Oak dining table, MTO-2026-00140, Completed, with a check mark, and Linen armchair, MTO-2026-00141, Waiting for Materials, with an empty circle.

Packing an order: the table is ready, the armchair still waits for its fabric.

 11 MTO orders, 4 completed, 75% on time, 9.1% canceled, 83.3% first pass in quality check, 18.2% waited for materials, average queue, production and lead times, throughput, and each maker's totals and lead time.

Four weeks of production, filtered by date.

Good to know

  • One MTO order is created per order item and MTO order type, for the whole quantity of the line: two armchairs on one line are one MTO order of two.
  • The Commerce order moves only when every MTO order of the type is in the state you chose. Canceled MTO orders are left out, so an order whose last unfinished MTO order is canceled moves on.
  • The Default MTO order type ships with automatic creation on a state named paid, which none of Commerce's own order workflows has. Choose a state of your workflow before relying on it.
  • The module creates no shipments. Staff create, split and ship them with Commerce Shipping, and an MTO order follows the shipments of its order item whenever one of the order's shipments is saved or deleted; an MTO order added by hand gets its shipment at the next such change.
  • Analytics count every MTO order on the site and measure times up to completion. Their on-time figures use MySQL and MariaDB date functions.

Additional requirements

  • Drupal 10 or 11, and PHP 8.1 or later.
  • Commerce Core 2.33 or later, or 3, with its Order, Log and Number Pattern modules.
  • State Machine 1.

Recommended modules/libraries

  • Commerce Quality Incident: its MTO integration sub-module opens a replacement or repair MTO order from a quality incident, which then goes out in a shipment of its own.
  • Commerce Shipping: shipment integration, the shipment form's MTO orders, and a ready-to-ship step for the Commerce order.
  • Commerce Order Amend: when an item is swapped for another variation, MTO orders still in Draft or Queued take the new variation, and for one already in production a note is logged on the Commerce order.

Community documentation

  • README: the workflow, both integration modes and hold states, analytics, permissions, the Drush command and the API.

Supporting this module

Developed and maintained by Bloomidea. Bloomidea offers support and custom development for this module.

Supporting organizations: 
Development and maintenance

Project information

Releases