New item setup (NIS)
New item setup (NIS) is the process a retailer, distributor, or marketplace uses to admit a new product into its catalog. The supplier files the item's identifiers, attributes, images, packaging data, and commercial terms; the buyer validates them against its category rules. Until the item passes, it cannot be ordered, listed, or shipped. Items are rejected when required attributes are missing, malformed, or contradict the manufacturer's spec sheet.
What new item setup is
New item setup (NIS) is the intake gate. Before a buyer's system will accept a purchase order for a 3/8-16 x 2 in. Grade 8 hex bolt, someone has to file the item: its GTIN, its MPN, the selling and ordering units of measure, dimensions and weight at every packaging level, country of origin, a category assignment, images, and copy.
It goes by several names. Item onboarding. Item setup. Vendor item form. New item request. The mechanics vary too: an Amazon flat file, a supplier portal, a GDSN publication, or a spreadsheet emailed to a category manager. Every version does the same job. It compares a submission against that buyer's category rules and returns accept or reject.
One asymmetry drives everything else. The supplier fills out the form, but the buyer owns the rules, and each buyer's rules are different. The same bolt has to be filed one way for a national distributor, another way for a marketplace, and a third way for a GDSN data pool.
What the buyer asks for
A category manager is not asking for "product data." They are asking for specific fields, in specific formats, with specific allowed values. For a single fastener SKU that looks roughly like this:
| Field | Example value | Typical rule |
|---|---|---|
| GTIN-14 | 10012345678902 | Valid check digit; unique per packaging level |
| MPN | HXB-3816-200-G8 | Must match the manufacturer's published spec sheet |
| Category | Fasteners > Bolts > Hex Cap Screws | Maps to the buyer's taxonomy, not yours |
| Thread pitch | 16 TPI | Controlled value, not free text |
| Length | 2 | Number and UOM in separate fields; UOM = in |
| Material and grade | SAE Grade 8 medium carbon alloy steel | Picklist value |
| Case pack | 50 EA per box, 8 boxes per case | Every level needs its own GTIN, weight, dims |
| Country of origin | TW | ISO 3166 two-letter code |
| Main image | Square, pure white background | Minimum pixel size set by the buyer; no lifestyle shot in slot 1 |
| Prop 65 | Yes/No plus warning text | Conditionally required |
Multiply that by a few hundred fields across a few dozen categories, then by every buyer you sell to. That is the shape of the work.
Why retailers reject items
Rejections are rarely about the product. They are about the file. The recurring causes:
- Missing required attributes for the category the item was assigned to.
- Wrong type or unit: "2 inches" typed into a numeric field, or weight sent in lb where the schema expects kg.
- Free text where a controlled value is required: "stainless" instead of
SS 316. - Identifier problems: a GTIN that fails its check digit, one GTIN reused across the each and the case, or an MPN that does not appear on the manufacturer's site.
- Packaging math that does not reconcile: case weight lower than the sum of the inners.
- Image failures: below the buyer's minimum pixel size, or a lifestyle shot in the primary slot.
- Claim violations: "UL approved" on a 600V wire connector when UL lists rather than approves.
- Wrong category node, which silently changes which attributes were required in the first place.
The cost is not the rejection email. It is the round trip. Each cycle burns days, and enough cycles push the item past the buyer's reset date or the season it was meant to sell in.
Where the work sits
Most teams already own a PIM. The constraint sits somewhere else.
| The PIM does this | Someone still has to do this |
|---|---|
| Stores attributes and their governance | Find the thread pitch that was never captured |
| Enforces required fields per family | Read the spec PDF and pull the torque rating out |
| Holds the buyer's channel mapping | Decide that "SS" means 316, not 304 |
| Exports the flat file | Normalize a dozen spellings of the same finish |
| Records the rejection | Fix every SKU that failed for the same reason |
The right-hand column is why new item setup stalls. It is research and judgment on thousands of long-tail SKUs, and it is usually done by a merchandiser at 11pm in a spreadsheet.
The PIM stores your product data. Anglera does the work of completing it: reading the manufacturer's spec sheet, filling the attributes the buyer's category requires, normalizing values to the buyer's controlled vocabulary, and flagging the ones a human should confirm. Anglera works alongside Akeneo, Salsify, Syndigo, inriver, and Pimberly rather than replacing them. The result is a submission filed against the buyer's rules rather than one guessed at.
Frequently asked questions
What documents do you need before you can file a new item setup?
Start with the manufacturer's spec sheet or cut sheet, because that is what the buyer will check the MPN and the technical attributes against. You also need the GTIN assignment for each packaging level, a packaging spec with weights and dimensions, certification or compliance documents such as UL or Prop 65 evidence, print-quality images, and the commercial terms sheet covering cost, MAP, and lead time.
Why do retailers reject new items?
Almost always for data reasons, not product reasons. The common causes are missing required attributes for the assigned category, values in the wrong format or unit, free text where a controlled picklist value is required, and invalid or duplicated GTINs. The rest come from packaging dimensions and weights that do not reconcile across levels, images below the buyer's minimum pixel size, and category assignments that pull in the wrong required-field set.
How long does new item setup take?
It depends far more on submission quality than on the buyer's queue. A clean file that passes validation on the first pass moves quickly. A file that gets kicked back starts a round trip: the buyer flags errors, the supplier hunts down the missing spec, resubmits, and waits again. Each cycle adds days, and several cycles can push an item past its planned launch window.
Who is responsible for new item setup, the supplier or the retailer?
The supplier does the work; the retailer owns the rules. The buyer publishes the category requirements, the field formats, and the allowed values, then validates against them. The supplier has to interpret those rules, find the data, and file it in the buyer's format. That is why the same SKU takes a different setup effort for every buyer you sell to.
Can a PIM handle new item setup on its own?
A PIM enforces and stores the requirements, and it will tell you a field is empty. It will not go read the manufacturer's spec sheet, decide the finish is zinc-clear rather than "zinc," or fill a torque rating that was never captured. That completion work is manual by default, and on long-tail catalogs it is what makes new item setup slow.