Operations

Operations connects a commercial agreement with what must be delivered, accepted, and reviewed. It is an operational workspace, not an accounting system, warehouse WMS, or legally complete ERP without additional configuration.

Main routes

• /operations/commitments for commitments and their cards;
• /operations/agreements for agreements and terms;
• /operations/orders for commercial orders, including new-order creation;
• /operations/catalog for catalogue offerings and specifications;
• /operations/connect for the one-screen setup of a published item for a client;
• /operations/fulfillment and /operations/acceptance for fulfillment and acceptance cases;
• /operations/services and /operations/supply for services, supply, and warehouses;
• /operations/billing, /operations/summary, and /operations/settings for invoices, the module summary, and settings.

Available routes and actions depend on permissions, organisation state, and the availability of working data. Keep an unavailable or not-ready state visible instead of replacing it with zeros or invented data.

The /operations/summary route returns either the complete set of figures or a whole-page error: if any source is incomplete or not ready, the portal says that the summary is not available yet and shows no partial metric cards. Missing figures are never zeros. When the message names a source, it says that the source is still preparing and asks you to retry in a minute; an ordinary load failure has a separate message. Some available metrics link to their corresponding registry: the portal carries the server-named worklist (worklist) and scope (scope) into the address instead of inventing a local filter. When a metric has no honest route (for example, payment reconciliation cases) or the server supplies no drill-down, the row remains plain text; do not treat its number as a link to a screen that does not exist.

Recommended workflow

1. Record the customer, supplier, or other commercial context.
2. Choose a published fulfillment profile and verify its human-readable name.
3. Open or create the agreement and commitment without changing terms blindly.
4. Prepare an order with catalogue items, quantities, an owner, and the expected result.
5. Send the items to fulfillment or supply.
6. Record acceptance, rejection, or a remaining quantity as a separate event.
7. Check related documents, tasks, invoices, and transition history.

The card should say who owns the next step, what is being handed over, and when the work is accepted. Attach a document or link in the working context when an external approval or proof is required.

Catalogue and fulfillment profiles

A catalogue item uses a published fulfillment profile. Do not infer an obligation type by rewriting a profile key or reading arbitrary text; use the name and type returned by the current contract. If the profile directory is temporarily unavailable, wait for recovery instead of creating an item blindly.

The agreement-terms editor shows the current lines and the fulfillment profile. The obligation type comes from the published profile, so you do not enter it manually. With write permission, revise the terms from draft; revising from review returns the agreement to draft. There is no separate return to an older version. If the catalogue or profile is empty or unavailable, wait for recovery instead of overwriting the agreement blindly.

Money, invoices, and currency

Operations may show prices, discounts, taxes, order totals, and invoices. Check currency, calculation source, rounding, and data status before comparing amounts. An empty field is not zero; use the amount displayed by the system instead of recomputing it in the browser.

Use synthetic amounts in training and state the organisation’s currency explicitly. Do not reuse money-bearing examples across languages without rechecking the calculation and currency label.

Errors and permissions

An empty list, a loading error, temporary unavailability, and an unavailable state are different. Check permissions, scope, filters, and reference data first, then retry. Do not bypass a limitation with external tools or create a duplicate after a partial success until history has been checked.

Safe demonstrations

Use a test organisation and synthetic customers, suppliers, products, amounts, and documents. Real account numbers, bank details, invoices, agreements, tokens, or customer data must not appear in documentation. Before a demonstration, check the interface language, currency, and absence of unnecessary personal data.

Related sections

• Operations catalog
• Registries, supply, and billing
• Commitment and agreement cards
• CRM
• Documents
• Tasks
• Disk and files
• Security and permissions

Set up a client

At /operations/connect, the portal takes a client and a published item through order creation, confirmation, fulfillment preparation, and (for a service) opening the first period. This is separate from the Connect action on an /operations/fulfillment row: that action connects an already-prepared fulfillment, while this flow creates the commercial setup. If the client has an active agreement, its line can be used for the client-draws-down cadence; otherwise choose a published catalogue item.

Form and consequences

Use the synthetic client Demo Client North and either Support hours — test or the agreement line Support package — test. The item’s frozen profile and price explain the quantity unit, carryover, overage, acceptance, and supply source; these consequences are not form settings. The cadence can be once, monthly, or based on an active agreement line. The result is shown as item quantity multiplied by the granted amount; do not type a total manually.

Billing is not a manual choice. The portal shows one of four bases—accepted quantity, period occurrence, order confirmation, or entitlement grant—and explains why the other bases are unavailable. If needed, use the synthetic legal entities LadVen Demo LLC and Demo Client LLC; separation of duties may require a second employee.

Errors, chain, and safe verification

The action runs order → submit → confirm → fulfillment → service connection. Each step shows loading, success, or failure. Retry the same step after a temporary read/write error; for a conflict, stale item, forbidden action, missing item, or unreadable plan, reread the source and do not create a duplicate. If nothing is published, the client has no active agreement line, or a legal entity is missing, fix the source data first. Do not promise one universal click count: a short path assumes the catalogue, client, and legal entities are already ready.

For documentation, use only these human-readable synthetic entities; do not submit the form or show real currency, account details, PII, tokens, or raw IDs. When money is visible, record currency.expected and currency.observed; do not call the chain successful without controlled mutation evidence.

Create an order from a CRM opportunity

The opportunity card menu enables “Create order” only when the pipeline allows conversion to an order and the opportunity has a company. If the pipeline purpose does not allow conversion or the company is missing, the disabled item explains the reason; do not bypass it with a direct URL. The client legal entity is normally sourced from the opportunity; if it is missing, the form can offer company options and save the choice back to the opportunity, or send you to fix the client card when no option exists.

From an opportunity card, open /operations/orders/new?opportunityId=<opportunityId>. The portal reads the opportunity and pre-fills its human-readable client, project, title and—when present—the client legal entity; the form still requires an offering, quantity, and provider legal entity. You can return to the pipeline while the form is open. The created order does not promise a backlink to the opportunity because its DTO has no such field, so verify the relationship in the source opportunity or activity feed, not by a technical ID. The “Order created” fact may reach the activity feed asynchronously; an immediately empty feed does not prove failure, and no delivery SLA is promised. If the opportunity changed, is unavailable, lacks a client/legal entity, or fails quantity validation, the form blocks submission and explains the correction; do not blindly repeat a POST. Use only synthetic Demo Client North, Rebranding — demo, Support hours — test, Demo Provider LLC, and Demo Client LLC; do not submit, show real amounts/PII, or expose raw IDs.