ormuz
Home/Integrations/Two/Nodes/Create back-office order (Two)
TwoConnecteurStable

Create back-office order (Two)

Creates or reuses a Two order from an Ormuz order originating from an ERP or back office.

Vue d’ensemble

Creates or reuses a Two order from an Ormuz order originating from an ERP or back office.

Exemple

Finance a B2B order created outside checkout and invite the buyer by email when Two requires verification.

Parameters 7

extension_config_idRequisref(extension_config:two)
Two configuration used for this operation. It determines provider identifiers, capabilities, and environment.
orderRequisOrder
Ormuz Order used as business source and durable mapping anchor for the Two order.
order_intentOptionnelTwo order intent
Optional Two pre-assessment whose tracking connects the order intent to final creation.
payment_terms_daysOptionnelenum
Payment term requested from Two for the financed sale.
invoice_typeOptionnelenum
Billing/financing mode requested from Two for the order.
order_originOptionnelenum
Declared sales origin at Two: online or in-store.
notify_channelOptionnelenum
Channel used by Two to invite the buyer to complete verification.

Outputs 5

orderTwo order
Latest normalized state of the relevant Two order.
payment_urlOptionnelurl
Two URL intended for the buyer for verification or payment initiation when provided by Two.
extension_object_mappingextension object mapping
Durable mapping between the Two object and its Ormuz anchor object.
createdboolean
Whether execution created a new Two resource/mapping instead of reusing an existing one.
selected_routestring
Normalized business state selected by the node; the route must be explicitly handled by the process.

Behavior

The node uses the order as anchor and may ask Two to send the verification invitation through the selected channel.

Limits and responsibilities

  • The notification channel does not replace Two verification itself.
  • The order remains subject to the states and decisions returned by Two.