Retailer files
The files retailers require, built from your ApparelMagic data and checked against it before they go out.
The problem
- Exporting from ApparelMagic, rebuilding the file in Excel, and getting it rejected over a dropped zero or a missing code.
- Hundreds of lines on a Nordstrom 886 checked against your records by hand.
- SKUs in ApparelMagic with no NRF size, filled in one at a time.
What it does
- GXS catalog files: pick the styles and the colors, lengths and sizes the retailer takes. UPC, NRF codes and the combined size token are filled in under the right selection code, ready to upload to OpenText.
- Nordstrom 886 checks: every line of an item setup or purchase order is checked against ApparelMagic and your price list, and corrections are written back into the original workbook. A store PO's dates, units and dollars are checked against your ApparelMagic order.
- Nordstrom IIF: the item form filled from ApparelMagic, one row per style and color.
- NRF sizes: the right NRF size code proposed for every SKU and written into ApparelMagic. It only fills blanks and never overwrites an existing code unless you say so.