Portal User Guide

Docs · Portal User Guide · Parts

Parts: create and edit records

Last updated: 29 July 2026Report an inaccurate guide

Use Parts to create and maintain product records. Each item has one Master Product, optional Site context, and stock location detail—see the portal data model.

Overview

Create or open a Master Product, then add Site and stock-location rows when stock is held in more than one place. Keep identifiers and descriptions accurate so warehouse scans and integrations stay reliable. Full hierarchy: portal data model. Prefer PartLogic SKU (and site or location SKUs where needed) over an unqualified "stock code". Summary also shows a Data Quality score for the record.

1. Open Parts

In the left sidebar, select Parts. From the Dashboard you can also use Search for parts or View parts →. Stock Search (/stock) lets you open a record by part or code—the same entry point used when superseding a duplicate.

Stock Search (/stock)—search by part or code to open a record.

2. Create a part

Start from Dashboard Create part, from Parts, or from the Uploader Create New Stock action on an unlinked row. Typical create fields include Description (with optional AI Enhance), Manufacturer and Supplier details, GTIN, and Primary Group. PartLogic automatically assigns a unique PartLogic SKU when the Master Product is created.

Create Part—Description with AI Enhance, manufacturer/supplier details, and GTIN / GPC identification.

3. Summary and Edit

After create (or when you open a part), the Summary tab shows PartLogic Part Number, Description, GTIN, GPC Category, manufacturer fields, and prices. Use Edit to change values. Other tabs commonly include Audit, Suppliers, Images, Attributes, Attachments, and Linked Parts.

Part Summary—master fields, Data Quality card, and Sites / Storerooms underneath.

4. Master Product fields

Master-level data holds the governed identity: PartLogic SKU, GTIN where available, categories, and core attributes. Prefer fixing master issues before inventing new Customer Site–only codes for the same physical item.

Master Product—one governed product identity for the organisation.

5. Customer Site fields

Under Sites, each row is a physical site or customer context with a Customer Site SKU, local part name, description, count, and price—while retaining a direct link to the Master Product. Use the site Edit control to adjust Site-scoped fields without replacing the master identity.

Customer Site—naming and Customer Site SKU scoped to that location.

6. Device / Storeroom fields

Expand a Customer Site to see Storerooms (devices). You can store a Device SKU, description, and location-specific information while retaining a direct link to the Customer Site record. Typical columns include Location, Physical count, Pack Size, and Min/Max. Edit device rows for local quantities and locations; mobile app work often targets these locations.

Edit Details on a Device / Storeroom row—location, Min/Max, pack size, and Save / Undo / Cancel.

7. Save and check quality

Save edits from the Edit controls on the relevant level. Re-check the Data Quality card on Summary—common warnings include missing manufacturer part number, invalid GTIN, or unassigned GPC. For broader scoring guidance see Good data practices and the Data quality guide.

Supersede, delete, and recovery

  • Supersede — use Duplicate Finder when two Master Products are the same item. The superseded SKU points to the keeper; historical movements remain associated with past transactions. Prefer supersede over creating a second master for the same part.
  • Delete an upload file — in Parts Uploader, deleting a file removes only the upload record, not parts already created from it.
  • Catalogue deletion / archive — irreversible removal of a Master Product can affect Site and stock-location rows, searches for the old SKU, and downstream integrations. Confirm the intended outcome with support@partlogic.co.uk before deleting live catalogue records.

Next steps

← Quick startParts Uploader →