Skip to main content

How to Update a SKU for Target (or other retailers) EDI and Ensure Inventory Sync Works

B
Written by Brendon Beebe
Updated over 3 months ago

Thanks! Here's the revised version with those updates: SKU obfuscated, no mention of Petal Lane, clarified that the channel SKU must be updated via import, and verification is done through the EDI report JSON:


How to Update a SKU for Target EDI and Ensure Inventory Sync Works

When selling through EDI to Target, making sure the correct SKU is sent is critical to avoid inventory showing as out of stock—even when everything looks right internally. Here’s a clear process to follow if you need to change the SKU that’s being sent to Target via your inventory system.


📦 What’s the Issue?

Let’s say Target has updated their records to use a new SKU for one of your items, and your team updated the SKU internally—but the item still shows as out of stock on Target.com.

That usually means the EDI inventory feed (846) is still sending the old SKU, which Target no longer recognizes.


🔧 How to Fix It

1. Understand the Two SKUs in Play

  • Internal SKU: The SKU used in your system (e.g. ABC-123-X).

  • Channel SKU: The SKU Target expects in EDI files (e.g. XYZ-987-Z).

Even if you change the internal SKU, the channel SKU mapping must also be updated so the right SKU is sent in EDI files.


2. Update the Channel SKU via Import

You cannot manually edit the SKU on the channel mapping page.

Instead, go to your Target channel in Luminous:

https://yourcompany.luminousolutions.com/channels/v2/[channel_id]/view

Then:

  • Use the “Import Channel SKUs” option to upload a CSV.

  • Ensure the CSV maps your internal SKU to the correct channel SKU (i.e., the new one Target is expecting).


3. Verify That the Right SKU is Being Sent

Once the import is complete:

  • Go to the EDI Reports section of Luminous.

  • Find the latest 846 Inventory Feed sent to Target.

  • Open the JSON payload and look for a line like this:

    {"sku":"XYZ-987-Z","internalSku":"XYZ-987-Z","upc":"1111","productName":"xxxx","availableQuantity":28453,"price":"","gtin":null}

    That XYZ-987-Z should match what Target has on file.

If the old SKU is still being sent, double-check the channel SKU import file and try re-importing.


✅ Best Practices

  • Confirm with your buyer (Target) exactly which SKU they expect.

  • Never assume that changing the internal SKU updates the EDI output—channel SKU mappings are separate.

  • Use imports only to update channel SKUs—manual edits are not supported.

  • Verify using EDI reports, not just your product list or internal inventory screen.


When in doubt, reach out to your support team or check your EDI logs to ensure the feed matches Target’s expectations. Getting this right ensures items stay in stock and orders flow smoothly.

Did this answer your question?