Skip to content

Attributes and documents

Capture a product’s technical specifications: each as a name, unit and value, so specs stay consistent across product families (for example a valve spec: bore, pressure class, flange standard).

  • Add, edit, reorder and remove attributes.
  • The unit picker offers common units and accepts a custom entry.
  • Duplicate attribute names within an item are rejected.

Apply a template: a named set of name+unit pairs, to add a whole spec set at once. Applying a template merges its attributes without overwriting existing ones. You can also save a new template from the current attribute set for reuse.

You decide which attributes are meant to appear in which documents:

  • Each attribute has a tick box per document type (for example quotation, technical datasheet, PO, invoice), so you can mark “Bore, Pressure, Flange” for a datasheet while leaving them unticked for the invoice.
  • Attributes can be organised into groups (Dimensions, Performance, Materials) and ordered within a group.
  • An attribute’s value can be overridden at the offer/order level without changing the master value, the override is stored against that offer/order only.

These choices, the per-document tick boxes, the groups and their order, and any offer/order overrides, are saved with the item, belong only to your organisation, and appear on the item detail.

Link document templates: design and spec files, to a product so its documents live with the item.

  • Each linked template carries a type (design / spec / certificate / manual / other) and an editable display name.
  • Files can be uploaded or selected from existing storage, and are previewable and downloadable in-app.
  • Templates can be reordered, and removing a link never deletes the underlying file.

Document links belong to your organisation, and files are stored in your organisation’s own area.

Define key-value pairs on an item to map it to external systems (for example a Tally item ID or a legacy ID).

  • A system-name picker offers presets (accounting, legacy ERP, ecommerce, other) and accepts custom values.
  • Each system + key combination must be unique on the item; duplicates are rejected.
  • Entries can be deactivated without deletion, preserving historic mappings.

Only a Tenant Admin can edit integration pairs.