What Is PIM When Amazon and Shopify Disagree

Amazon calls the lamp brass. Shopify calls the same SKU gold. The photo is yours on both sites. What is PIM is the record that says which finish you actually approved, before either title goes out. A spreadsheet with a tab per channel will not settle that. Each tab can be edited by a different person on a different afternoon. What is PIM? It is the approved record for one product: the identifier, the specs, and the words you will stand behind. You edit that record, then each channel gets a mapped copy. On-hand quantity is a different system. A folder of images is a different system too. Shopify's PIM guide says the store admin can add products, update prices, and use metafields, and that this is not a dedicated PIM system. The guide lists the point where that admin gets thin: more than one channel, a large catalog, or more than one version of the content. What belongs on the record, and what does not? GS1 US defines a GTIN as a GS1 identification key for a trade item, the product you sell in a marketplace listing or a store. The number identifies the item. It is not the finish, and it is not the title. Put it on the record so every channel is talking about the same lamp. System What it should hold What it should not decide Product record Finish, height, bulb, weight, GTIN, approved text How many units are free to sell Inventory On-hand, reserved, inbound Which title Amazon displays Image files The photo file itself Which photo is approved for which channel Store admin The live listing after you publish A second channel's required attribute On-hand of 18 is a warehouse fact. Finish brass is a catalog fact. If you type 18 into the product record and call it the listing quantity, the next order will not reduce it. Sellable quantity stays in inventory management. What does one lamp look like? Call the SKU LAMP-14. These values are an example, not a supplier feed. Field Approved value Finish Brass Height 14 in Bulb E26 Max watt 60 Weight 4.2 lb Identifier The GTIN you were issued for this item Amazon's title, in this example, is "Example Brand Brass Desk Lamp, 14 Inch, E26." Shopify's title is "Brass Desk Lamp." Both can be true at once. They are display strings. Finish is still brass on the record. Someone on the Shopify team renames the page "Gold Desk Lamp" because a buyer asked. If that edit writes back into finish, Amazon's next update says gold too. A title change is not a spec change. Finish moves only when you edit finish, on purpose, in the record. If the finish lives in three cells, you do not have what is PIM yet. You have three opinions. Which words are allowed to differ by channel? Field Where it lives Rule Finish, height, bulb, weight, GTIN The record One value. Channels receive it. Title A channel copy May be shorter or longer. Must not contradict the record. Price Often a channel copy Example retail $80 is not a spec. Do not store it as finish. Required attribute a channel adds Mapped from the record If the record has no value, the send waits. A channel that wants finish as its own column still reads brass from the record. You do not retype brass into a notes cell and hope the feed finds it. AI product information management in OneChannelAdmin is that record. Publishing the mapped title is multichannel commerce. The Shopify page that receives a copy is the Shopify integration. When is a spreadsheet still enough? One store, one editor, and a screen where you can see every attribute. You can keep the lamp in a sheet. I would not add a second channel on top of that sheet. The failure is specific. Amazon shows brass because column D says brass. Shopify shows gold because a different tab was never updated. Both listings look complete. The buyer who saw both will not file a ticket with your spreadsheet. They will doubt the lamp. A second channel also asks for a field the first channel never showed. The empty cell looks harmless until the feed rejects the row, or worse, publishes a blank spec. That is the week the record earns its keep. Who may change the finish? One named editor, writing on the record. A marketplace rejection is not permission for support to type a new finish into the channel portal. The portal edit feels fast. The next send puts the record's value back, or it publishes the portal's typo everywhere. Walk the gold title. Shopify becomes "Gold Desk Lamp." Finish stays brass. Amazon can still say brass, which matches the record, and the Shopify title is now the contradiction you revert. If you "fix" Amazon to gold so the sites match, you have copied the mistake and called it consistency. Photos follow the same split. The file can sit in a folder. The record names which file is the main image. Replace the file in the folder and forget the pointer, and the next publish sends the old photo with a new filename you only think you swapped. A black lamp is not a title tweak on the brass record. It is a second SKU with its own finish. If both finishes share one identifier, you told every channel they are the same trade item. GS1 US describes that identifier as the key for the item you sell. Two finishes need two keys. Write the editor's name on the record when finish changes. "Updated from the portal" is not a name. Six months later you will not remember who turned brass into gold, and both live pages will look intentional. Count the fields you would defend in a support ticket. For this lamp the list is finish, height, bulb, max watt, weight, and the identifier. Title length is not on the list. A buyer who asks why the Shopify name is shorter than Amazon's has a layout question. A buyer who asks why one page says gold has a record question. Answer the second from the record, then fix the title that contradicted it before you reply. Do not answer by editing whichever page the buyer happened to open. Store the date of the last spec change next to the editor's name. A title edit does not count as that date. If you cannot find the date, the gold title is about to happen again. How do you create the first record? Pick one SKU that already disagrees across two channels. LAMP-14 is enough. Write the fields you will defend: finish, height, bulb, max watt, weight, and the GTIN. Mark title and price as channel copies, not as the spec. Point Amazon and Shopify at those values. Do not let a title edit overwrite finish. Publish. Read both live pages against the record, not against each other. Change height to 15 in on the record only. Confirm both channels show 15, and that finish stayed brass. Stop on step 4 if a Shopify rename changes the Amazon finish. You are still editing listings, not a record. Questions about the product record Is a PIM the same as inventory? No. Inventory says how many lamps you can ship. The product record says what the lamp is. An on-hand count of 18 does not tell Amazon the finish. Is the Shopify admin a PIM? Shopify's own guide says adding products, prices, and metafields is not a dedicated PIM system. The admin is where one store publishes. It is not the place that also owes Walmart a different required field. What is the GTIN for? GS1 US describes it as the identification key for the trade item. Use it so each channel refers to the same lamp. Do not invent a second code per site. Can the title differ by channel? Yes. A shorter Shopify title and a longer Amazon title can share one finish. The title must not smuggle in a new spec. Gold in the title, while the record says brass, is a contradiction. When should you leave the spreadsheet? When a second person, or a second channel, can change a spec without the other place changing too. One editor and one store can live in a sheet. The brass-versus-gold lamp cannot. OneChannelAdmin Team writes about product records, channel titles, and the specs a listing still has to match.