Catalogue
The catalogue lists all the products an organization can request, order, and distribute at its events: signage material, aid station supplies, safety equipment, etc.
Features
- Product inventory, organized into hierarchical categories.
- Each product has an active or archived status — a product is never deleted, only archived, to preserve the history of past requests and orders that reference it.
- The catalogue is global to the organization: it is not specific to one event, and is not duplicated from one edition to another — all editions of the same organizer share the same catalogue.
Default budget allocation
Each product has a default budget allocation, which determines which budget is impacted when a sector requests this product:
- Requesting sector (default): the budget of the sector making the request is impacted.
- Logistics (shared): the Logistics budget is always impacted, regardless of the requesting sector — for shared material (e.g. barriers, grandstands).
This allocation automatically pre-fills the request line; the logistics coordinator retains the ability to correct it on a case-by-case basis during processing. See Budget & Sponsors.
Product packaging
A product can specify a unit of use and a unit of sale, a quantity per package, as well as a usual deposit container (e.g. a crate or a pallet) it is associated with. This information is indicative: the quantity of containers to receive or return is always entered manually during stock movements.
Suggested accessories
A product can declare the accessories that almost always accompany it, along with their ratio: 4 rubber pads per half-muba, 2 straps per barrier. This is declared once, on the product sheet.
Then, as soon as a sector adds this product to a request, the missing accessory is suggested to them, with the quantity already calculated based on what they put in the cart (10 half-mubas → "40 × Rubber pad"). One click adds it, another dismisses it.
Three points to know:
- Nothing is added automatically. It's a suggestion: the sector sometimes already has the pads, and a line appearing on its own would be an unexpected expense discovered on the invoice.
- The added line then becomes a line like any other: quantity, location, period, and priority remain editable, and it no longer follows the quantity of the product that triggered the suggestion. Changing the number of half-mubas does not recalculate the number of pads.
- An accessory does not trigger its own accessories. Only the accessories of the products actually requested are suggested — the chain doesn't unfold any further.
The same suggestion appears everywhere a request is built: the Sector space, the Logistics space, and the mobile app.
Serial number tracking
A product can be marked unit-tracked: each item is then identified by its own serial number (e.g. radios), rather than being counted globally. This is in particular what allows the Depot Kiosk to know precisely which radio was taken.
Units are normally created automatically upon receipt of a supplier order. For material already owned before using TriLog (e.g. an association's existing radio fleet), serial numbers can also be entered manually from the product sheet, Units tab — without going through the request → order → receiving cycle. Each manual addition or removal automatically generates the corresponding stock movement, so that the displayed stock always matches the number of recorded units.
A unit created from a supplier receipt cannot be deleted from this tab (the finalization of the related receipt must be cancelled instead); a unit that has already left the depot, or that has a history of pickups at the kiosk, cannot be deleted either — it must be marked lost or broken instead.
Where to find it
The catalogue is managed from the Admin space (creating, editing, archiving products); it is viewed read-only from the Logistics space when creating orders, and by sector members when creating a request.
Products and categories can also be bulk imported from an Excel/CSV file, from the Admin space — an action reserved for organization administrators. See the bulk import tutorial.
Archiving a product removes it from selection lists for new requests, without affecting existing requests and orders that already reference it.
Full step-by-step guide: see the tutorial →