Items, units, groups and vendor items

Review purchase-item import validation errors

Correct rejected item rows using the import result/error file. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Purchasing staffPermission: purchase_items or purchase_vendor_items capabilityModule v1.7.9
Jump to steps
Where to goAdmin Area → Purchase → Items → Import results
Before you start
  • Use an account with purchase_items or purchase_vendor_items capability and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What you’ll accomplish

Correct rejected item rows using the import result/error file. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Purchase → Items → Import results.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

Fields and options to review

Item masterCommodity/item code, description, group/subgroup, unit, purchase price, tax and purchase eligibility.
Vendor-item mappingVendor, group and selected item list, shared visibility and vendor-specific values where exposed.
Files/importAttachments, spreadsheet import rows, validation errors and generated barcode/code.

Rules the system enforces

  • Item and vendor-item operations use separate capability groups.
  • Spreadsheet imports can create an error file for rejected rows; review it before retrying.

How to confirm it worked

  • The supported review purchase-item import validation errors flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.