Skip to content
P4 Software P4 Software / logisticaHQ-en

Add these docs to Claude

Ask Claude questions about these docs. Claude reads the published pages and links you back to them. Copy this address:

https://p4-software.opendocs.page/mcp

In claude.ai or Claude Desktop: open Settings, then Connectors, choose Add custom connector and paste the address.

In Claude Code, run:

claude mcp add --transport http docs https://p4-software.opendocs.page/mcp

Required product fields and allowed units

Available from version 2.64.14.

LogisticaHQ lets your Warehouse decide which product fields must be filled in before a product can be saved, and which units of measure Products may use. You set the rule once for the whole company, and you can give any 3PL client its own rule on top of it. When a rule is set, every place where Products are created or changed follows it: the product screen, the New product window, the Excel import, the client portal and the systems connected to LogisticaHQ.

The same section also covers what happens to the automatic 3PL invoice of a client who is billed by weight or cube when some of that client's Products have no weight or dimensions: the invoice is put on hold instead of being created with wrong figures.

When to use it

  • Your 3PL bills a client by weight or cube. Every product of that client needs a length, width, height and weight, each with its unit, or the invoice cannot be calculated correctly.
  • Your company only works in inches and pounds. You allow only those units, so nobody saves a product in centimeters or kilograms by mistake.
  • You need every product to carry a barcode, a category or customs data (HTS code, country of origin) before it is stored.

If you set nothing, Products, imports and integrations behave exactly as before.

How the two levels combine

Level Where you set it What it does
Company Configuration > Business > Products Applies to every product.
Client The client's record (Tenant staff only) Adds required fields for that client's Products, and can replace the allowed units for that client.

For one product, LogisticaHQ looks at the product's client:

  • Required fields are the company list plus the client's own list.
  • Allowed units are the client's own list if the client has one; otherwise the company list.
  • A product with no client follows the company settings only.

Empty means no rule. An empty required-fields list requires nothing, and an empty units list allows all units.

The pages in this section

  1. Set the company rule
  2. Set a rule for one client
  3. Working with products under a rule
  4. 3PL invoices on hold

The rule in short

  • A new product that is missing a required field is refused.
  • A product that is already saved is refused only when a save would empty a field that holds a value. A required field that was already empty may stay empty, so Products saved before the rule existed can still be saved. Fill the field in when you can; once it is filled in, it cannot be emptied again.
  • For a number (length, width, height, weight, unit cost), 0 counts as empty.
  • Requiring Length, Width or Height also requires the length unit. Requiring Weight also requires the weight unit.
  • A product that is controlled by Decimal quantities is measured by its unit of measure. It is never asked for dimensions, weight or their units.
  • A unit that is not on the allowed list is refused, unless it is the unit the product already has. A product keeps its current unit until someone changes it.
  • A product moved to another client is checked like a new product against the new client's rule.

Connected systems (ERP and other integrations)

Systems connected to LogisticaHQ, such as an ERP, are held to the same rules as people when they create a product: a new product that misses a required field is refused. When a connected System updates an existing product and sends a blank (or 0) for a required field that the product already has, the blank is ignored: the stored value stays and the rest of the update is saved as usual. A blank for a field that is not required still clears it, as before.

Unit cost is never required of a connected System, because these systems have no way to send it. A product created by an ERP without a unit cost shows under Incomplete for the office staff if Unit cost is required. A connected System can ask LogisticaHQ which fields and units apply to a client before it sends anything.

Common questions

Why can't I save this product? The rule of its client (or the company rule) requires something the product does not have, or the unit you chose is not allowed. LogisticaHQ shows a message that names the product and the fields. Fill them in and save again. See Working with products under a rule.

Why was my import row refused? The import checks every row against the same rule. In the import window, the list of rows that will not be imported gives the sheet row, the SKU and the reason. Correct the file and import it again. See Working with products under a rule.

Why was this month's invoice not created? The client is billed by weight or cube and some of its Products have no weight, dimensions or unit. The invoice period is on hold. Open the client's billing profile to see the held periods and the reason, fill in the Products, and the invoice is created on its own. See 3PL invoices on hold.

How do I see which Products are incomplete? On the Products list, press Incomplete in the Needs attention tile above the list. The list shows only the Products that lack something their client's rule requires. Open a product to see what is missing. See Working with products under a rule.

Was this page helpful?