Portail ZAPP

Administering orders

Available in en es fr

Updated on 10/25/2026

Order settings are in CRM › CRM administration › Orders (address: /crm/admin/orders), reserved for Administrators and CRM administrators.

General settings

  • Number prefix: an order number is this prefix, the year and a counter (SO2026-00042). The counter restarts at 1 every year.
  • Internal hourly cost: the cost of one hour of work, in the catalog base currency. It is used for the actual margin: hours logged on the order's project × this cost. Leave it empty not to count time spent.
  • Default project type: the type given to the project when the "project" rule does not specify one.
  • An accepted quote creates its order and runs the handoff: checked by default. Uncheck it to create orders by hand from the quote.

Handoff

Each action is enabled separately. An enabled action whose module is not installed does nothing (it shows as "Not applicable" in the order log).

  • Billing: installments are requested from the billing module when due (scheduled task CrmOrderBilling, every morning), each only once.
  • Project: creates a project when a product sold matches a "project" rule.
  • Stock and purchasing: reserves the stock items linked to the products sold; any shortage becomes a replenishment proposal, which purchasing turns into a purchase order.
  • Support contract: adds the hours sold to the customer's support contract (prepaid pack), or creates a prepaid contract.
  • Subscriptions: tracks each recurring line as a subscription, with its commitment end and renewal date.
  • Client contract (off by default, needs the Contract management module): creates a client contract for the recurring lines — starting on the order date, ending at the latest commitment end, renewed automatically if every product renews by itself, explicitly otherwise — and links the order's subscriptions to it. Their renewal is then read on the contract, never twice.

Handoff rules

A rule links a product or a product family to an action:

Action Parameters
Project Project type (optional; otherwise the default type)
Support contract Support minutes per unit sold, credit validity in months (12 by default)

The product rule takes precedence over its family's; between two rules at the same level, the order decides. Example: the "Hardware" family creates a "Deployment" project; the "10 h support pack" product credits 600 minutes per unit, valid for 12 months.

Applies from version 1.0 Verified for version 1.0

Was this article helpful?

Still need help? Create a request