A product is any item myWork tracks - raw material, a cut or welded part, an assembly, a finished good, a container, a consumable, or even a purchased service. Products are master data owned by Unleashed (our ERP). myWork keeps a local copy so you can browse, classify and report on products quickly, and - with the right permission - push changes back to Unleashed.
Knowing which data lives where is the one thing to get right.
Where the data lives
Unleashed is the source of truth for the core product fields: code, description, unit of measure, prices, dimensions, supplier and the obsolete flag.
myWork pulls those fields on a schedule and on demand. A pull overwrites the local copy - so never hand-edit an ERP field expecting it to "stick" locally.
Creating or editing a product's ERP fields pushes to Unleashed first, then saves locally. That needs the PRODUCT_WRITE permission and is a real ERP change - there is no local-only edit of an ERP field.
A set of fields is myWork-local only and is never pushed: category, tags, attributes/specs, usage classification, manufacturing method, repair and assembly area, online-shop flag, internal notes, product image and the Bill of Materials. These survive every sync and are safe to refine any time (permission PRODUCT_EDIT_BASIC).
The practical rule: classification is local and safe; the description and other ERP fields are shared master data and push to Unleashed.
The product page
Open a product from Products → Product List (see Finding products: search, filters and the faceted browse). The page shows a hero image and a read-only classification summary (category, tags, specs), then tabs:
Product Info - the ERP fields. Editable only with PRODUCT_WRITE, read-only for everyone else.
Classification - the local fields: category, Tags, Internal Notes, Usage classification, Manufacturing method, Repair Area, Assembly Area, online-shop flag and the category's attributes. Save Classification stores them locally and never touches Unleashed.
Stock & Pricing - availability and, for permitted users, prices.
Relationships - related products.
Attachments - drawings, flat patterns, 3D files, photos.
Used In BOMs - the parent assemblies this product is a component of.
Own BOM - what this product is built from.
Conversions - unit and product conversions.
Suppliers - supplier links and supplier codes.
Cost - cost breakdown, shown only to cost viewers.
Two save buttons, two scopes: Save Classification (local, safe) versus Save & Push to Unleashed (ERP, needs PRODUCT_WRITE).
Usage classification
The Classification tab carries a Usage classification field: what the item is used as (stock to sell, equipment, a fixed asset, a consumable and so on). It picks from the classification-category catalog maintained by Finance; the finance treatment is derived from it rather than chosen here. The default is "— Use category default —", which inherits the category's setting, and the tab shows the effective value underneath ("Not classified — Finance decides on first request" if nothing applies). See Classification Categories and Classifying a product: categories, attributes and tags.
Adding a product photo
The photo is set on the photo tile at the top left of the product page - the same tile that shows the picture once there is one. You need PRODUCT_EDIT_BASIC; without it the tile is only a placeholder.
There are three ways in, and they all do the same thing:
Click the tile to browse for a file. On a phone this offers the camera, so a product can be photographed where it stands.
Drag a picture onto the tile from your desktop, a folder, or another browser window.
Press Ctrl+V to paste a picture already on your clipboard - from a supplier datasheet, an email, or a screenshot - without saving it as a file first.
Paste is deliberately narrow. It only lands while the tile is under your pointer or selected (click it, or Tab to it), and for as long as it will, the tile shows a small Ctrl+V badge. An image you copied for something else is never swallowed by the product page.
Once a photo is set, hover the tile for change and remove. Changing it accepts the same three ways in.
Two things worth knowing:
The photo is myWork-local. It is never pushed to Unleashed, so setting one is safe whatever your ERP permissions are.
Large photos are shrunk in your browser before they are sent, so taking one on a phone out on the floor is quick even on a weak signal.
The photo appears wherever the product does - product lists, the pick, collect and receive screens on the floor, My Store and the online shop - which is why a product without one is worth fixing when you notice it.
The photo also lands in Attachments, tagged Primary. Uploading there and promoting an existing image to primary still works, and remains the way to reuse a picture you have already attached to the product.
Who can see and do what
PRODUCT_READ - view products (no prices).
PRODUCT_PRICE_READ - reveal money (sell price, cost, margin). Floor and stock-mover screens never show prices - currency appears only on the product and sales pages, and only to users who hold this. It is implied by PRODUCT_WRITE, PRICEBOOK_MANAGE and the cost-report permissions.
PRODUCT_EDIT_BASIC - edit the local classification, and set the product photo (never pushes). This is the "classifier".
PRODUCT_WRITE - create and edit ERP fields (pushes to Unleashed).
PRODUCT_CATEGORY_MANAGE - curate the category tree, attributes, tags and methods (see Managing the product taxonomy (steward guide)).
Suggested roles: Product - Viewer, Product - Viewer (Pricing), Product - Editor (the classifier) and Product - Manager (full).
Creating a product
Create from the Products → Product List page (New Product, shown to PRODUCT_WRITE holders). Two things are mandatory and carry all the meaning:
a real description, written to the naming convention, and
a category.
The product code is auto-generated (for example MW-5874-9855) - do not hand-craft codes or encode material/size into them. A product image is strongly recommended - see Adding a product photo above. See Classifying a product: categories, attributes and tags for how to name and categorise.
Related
Classifying a product: categories, attributes and tags - categories, attributes, tags and the decision procedure.
Finding products: search, filters and the faceted browse - search, filters and the faceted browse.
Managing the product taxonomy (steward guide) - for the master-data steward.