Help

Get practical support for inventory upload, supply needs, quotes, orders, delivery proof, invoices, documents, and network requests.

Available
Help
Open inventory

Help detail

Upload Inventory Catalogue

Prepare a CSV, Excel, or PDF catalogue so active project needs can match to available stock.


Sections

OverviewLinked recordWorkflowEvidencePacketLifecycleWhat to includeAfter uploadFactsGuardrail

Help record

Upload Inventory Catalogue

Prepare a CSV, Excel, or PDF catalogue so active project needs can match to available stock.

Available
Linked record

Inventory

Record signal

Available

Status

Available

Next gate

Open inventory

Linked record context

This record is kept tied to its governing object so state, source, and next action remain clear.

Linked record

Inventory

FieldWhy it mattersSignal
Linked recordPrimary object this record is tied to.Inventory
Record signalThe main amount, package, delivery, or capital signal to inspect.Available
StatusCurrent visible state for this role.Available
Next gateNext allowed action or review step.Open inventory

Help workflow

Review the record summary, status, related facts, evidence, and next gate before taking action.

1

Product name

2

Category

3

Available quantity

4

Lead time

5

Delivery area

6

Certification notes

Evidence and source path

Evidence should stay near the decision it supports and remain visible to the right role only.

1

Product name

2

Category

3

Available quantity

4

Lead time

5

Delivery area

6

Certification notes

Record packet

The record packet keeps the visible facts, source state, and allowed action in one place before the user moves deeper into the workflow.

Record state

Available

SignalVisible valueWhy it matters
Linked recordInventoryShows the governing object this record belongs to.
Record signalAvailableHighlights the main value, delivery, capital, or performance signal.
Next gateOpen inventoryClarifies what the user can inspect or do next.
Source stateSource-backedKeeps placeholder, source-backed, and planned integration data separate.
VisibilityPermissioned Register viewProtects private bids, quotes, payments, and restricted diligence fields.

Record lifecycle

This record follows a source-backed review path before any governed action is taken.

StageOwnerSignalState
Record openedRegisterInventory
Complete
Current stateUserAvailable
Available
Next actionUserOpen inventory
Next
Decision supportReviewerEvidence and source boundary
Pending
OutcomeGoverned workflowHuman-controlled outcome
Planned

What to include

A useful catalogue gives the matching engine enough product, stock, and delivery information to identify strong supply needs.

Product name
Category
Available quantity
Lead time
Delivery area
Certification notes

After upload

Matched needs appear in Supply Needs and can be opened before starting a quote package.

Applies to

Inventory and supply need matching

Accepted formats

CSV, Excel, or PDF catalogue

Optionality

Inventory upload improves matching but is not required to browse needs

Privacy

Supplier-provided catalogue data remains permissioned

Record facts

Applies to

Inventory and supply need matching

Accepted formats

CSV, Excel, or PDF catalogue

Optionality

Inventory upload improves matching but is not required to browse needs

Privacy

Supplier-provided catalogue data remains permissioned

Governed action guardrail

Atlas may summarize this record, explain gaps, and draft questions. It cannot approve, deny, publish, pay, award, select, or execute the next governed action. Human owners remain responsible for every decision gate.