An item master migration should establish how each product or service behaves in purchasing, inventory, sales and accounting. A successful import of item names and codes does not prove that stock can be received, fulfilled, valued or reported correctly. Design the target item types and dependencies before loading the complete catalog.
Separate item master setup from opening stock. The master defines the item; the opening-stock process establishes quantities and value under the approved inventory design. Combining these concepts without checking supported behavior can leave a catalog that looks complete while inventory detail is missing.
Inventory the source catalog and identify stock, non-stock, service, assembly, kit and other relevant categories. Confirm whether the business buys, sells or both buys and sells each category. Record whether traceability by lot or serial number is required.
Have operations and finance approve the target classification together. An item type affects more than the appearance of the record; it influences the process and accounting design. Do not choose a type solely because its label resembles the source-system category.
Oracle lists the item record types supported for import, including distinct inventory, assembly, non-inventory and service categories. Use the documentation for the chosen type and enabled features when building the mapping.
Choose a stable target item identifier and preserve the source crosswalk. Distinguish internal identifiers, displayed item codes, supplier references and customer-facing codes. If several source systems use different codes for the same item, define how each will resolve to the authoritative target.
Review units of measure carefully. Record purchase, stock and sale units, conversion factors and rounding expectations. Test an actual purchase and fulfillment example where units differ. An apparently small unit error can multiply quantities or costs across many transactions.
Check special characters, leading zeros and duplicate codes before import. Keep names and descriptions readable, but do not rely on them as the only integration key. Coordinate any item renaming with downstream systems.
Identify required income, expense, asset and cost-of-goods-sold accounts according to item type and the approved accounting design. Oracle's item account guidance explains that acceptable account references depend on the item type; an invalid mapping can fail import.
Review subsidiary availability, location behavior, tax treatment, pricing, preferred vendors and relevant planning settings. Confirm which values belong to the shared item and which are maintained by subsidiary or location under the chosen features.
For assemblies, validate component relationships and the intended bill-of-materials approach. For kits or groups, verify the required member relationships. Load dependencies in a deliberate order and test a representative end-to-end transaction before scaling up.
Oracle's Notes about Items Imports states that the Inventory Detail subrecord is not supported through item imports when Advanced Bin / Numbered Inventory Management applies. That subrecord carries detail such as bin and lot or serial quantities. Do not assume an item CSV will establish a complete traceable opening-stock position.
Identify the supported transaction or process for your opening quantities and inventory detail, and validate it in the account's current configuration. Have the controller approve the resulting valuation and ledger effect. The appropriate method depends on features, item types and the migration design.
Reconcile physical quantities independently of monetary value. Define the stock-count cutoff and how movements during cutover will be captured. Inventory that is in transit, committed, damaged or held for another party may need specific treatment and operational review.
Where matrix items are used, establish the option structure and parent-child relationships before importing the corresponding item data. Oracle's supported item import guidance notes that matrix options need prior setup through custom lists and item fields.
Review the relationship between ERP items and commerce variants. Ensure every sellable variant resolves to the intended item and that discontinued variants are treated consistently. A catalog migration should not reactivate obsolete items accidentally.
Document attachments, images and extended descriptions separately if they are in scope. Their presence in a source catalog does not establish that they will travel through the same item import. Assign owners and acceptance checks for each additional asset population.
Select samples that cover the actual catalog complexity: a simple stock item, a service, a purchased-and-sold non-stock item, an assembly, a matrix variant and a traced item where relevant. Include different units and account mappings.
For each sample, test the intended purchase, receipt, sale, fulfillment, return and adjustment processes as applicable. Inspect quantities, statuses, price behavior and financial impact. Confirm that integrations and reports use the correct target identifier.
Review inactive and restricted items as well as active ones. Users should be able to find historical references without accidentally using an item that should no longer be available for new business.
A distributor buys a product in cases of 12 and sells individual units. It also tracks serial numbers. The migration team first approves the item type, unit relationships and source-to-target code mapping.
The opening-stock design then establishes 24 individual units with the required serial detail through the supported tested process. A sample purchase of one case and a sale of two units verify the conversion and traceability behavior. The item record being present is only one part of the evidence; the quantity, serial population and valuation must also reconcile.
Use this closeout checklist:
Assign permanent ownership for new items and changes after launch. A clean starting catalog will deteriorate if departments create records without shared rules. Treat migration as the first use of a sustainable item-governance process, not a one-time spreadsheet exercise.