Service terms

Ordinon is provided to business customers under an agreed order form or service agreement.

Business service

Scope and commercial terms are agreed in writing.

Human approval

Your team reviews and approves prepared orders.

No purchase by enquiry

Asking for a quote creates no paid subscription.

This overview explains how the service is used. Your written customer agreement defines the applicable commercial and data-processing terms.

Service scope

Your written agreement defines the order volume, configuration, output, support, fees and responsibilities for your workspace. A quote request does not create a paid subscription or commit you to purchase.

The agreed scope should identify the accepted document types, reference data, approval process and required order output. An ERP name in an article or product discussion does not establish that a connector, field mapping or direct submission workflow is included in your service.

Authorized access

Access is for authorized users within the customer workspace. Keep credentials secure and notify us when access needs to be removed or may have been compromised.

The customer identifies the people permitted to use its workspace and the reference records they should use. When responsibilities change, review access and the ownership of approval and ERP import activities.

Order review

Customers must have the right to process uploaded content and reference data. Your team is responsible for reviewing prepared orders, resolving exceptions and deciding whether an order is approved for export.

AI-prepared values can be incomplete or incorrect. Review the original source and the applicable customer, item, unit and commercial records. Approval applies to the saved version; it is the customer’s decision that the order is ready for the agreed next step.

ERP imports and connections

Approved orders are available as CSV exports for the customer’s ERP import process. Your implementation must establish the destination fields, required identifiers, duplicate handling and how to confirm that the ERP accepted the order.

Where catalog API access is configured, the customer supplies authorized access and agrees the record mapping. Direct API order delivery is separately scoped and must be validated against the receiving system. Successful file export alone is not confirmation of ERP acceptance.

Acceptable use

Do not bypass access controls, interfere with service operation or upload malicious or unlawful content.

Use the workspace for the agreed business workflow and respect the displayed file and processing limits. Do not attempt to access another customer’s records or share credentials with unauthorized people. Report a suspected access issue through the security contact.

Report a security issue

Commercial and data terms

Service levels, liability, intellectual-property rights, data processing, retention, termination and governing law are defined in the applicable written agreement.

[email protected]
Questions about this information?Find the right contact