Parkson consignment · standard operating procedure
How a promoter’s finished worksheet becomes keyed sales in IDCP, and the three numbers to check before you press import.
| Thing | Where |
|---|---|
| The CSV from the promoter | WhatsApp or email — the file called
<outlet>-august-full-ticket.csv |
| The tool | Dropbox\Claude\shared\MR_S\parkson-b2b-skill\RUN\ |
| IDCP | The consignment sales screen for that outlet |
Desktop is fine. Do not open it in Excel first. Excel rewrites the dates and the separators; the tool copes with that, but it is one less thing to go wrong.
Use the larger / later one, and check its total before you go on. Two downloads happen when she saves once part-way and again at the end. The tool prints the total, so if it does not match what Parkson rang, you have the wrong file.
MAKE IDCP IMPORT.batIn the RUN folder. A black window opens and does the work. It takes about a
minute.
It figures out which outlet the file is from by itself, from the location codes inside it. You do not tell it anything.
What it is doing
The window ends with a CHECK block. All three must be right or you stop.
| Line | Must say | If it does not |
|---|---|---|
| money | the same total Parkson rang for that outlet that month | wrong file, or the promoter has not finished. Do not import. |
| rows without a barcode | 0 | send the list back — those lines will not load |
| rows discounted but with NO code | 0 | the money would be right and the discount wrong. Ask before importing. |
A fourth line, “rows where no size was given, so it was resolved for her”, is not an error. It lists the lines where the size came from how that outlet keys that garment normally. It is there so you can see it, not so you can fix it.
The tool writes both. Use whichever suits the job.
| File | Use it when |
|---|---|
IDCP_Multilocation_Import_<month>.xlsx |
Normally. Whole month, every counter, one import. Keyed on the barcode. |
by item code – one per ticket\ |
When you are keying into an existing daily ticket. One file per counter per day, because that layout takes one location code at a time. |
Open the consignment sales import for that outlet, choose the matching template, upload the file, and let it validate before you commit.
Do not edit the file by hand to make them pass. Note which rows and send them back — a rejection almost always means an item code or a barcode that no longer exists, and forcing it through puts the sale on the wrong garment.
After importing, the outlet’s keyed total should equal what Parkson rang, to the cent. Counter by counter, not just the store total.
Subang Parade, August 2026, after import:
BYFORD 24,482.10 = 24,482.10 FOREST 13,560.14 = 13,560.14 KIDS 6,477.50 = 6,477.50 LADIES SOCKS 3,642.30 = 3,642.30 LADIES 2,635.80 = 2,635.80 AGAINST 2,434.59 = 2,434.59 TOTAL 53,232.43 = 53,232.43
Her answers live only in her own browser. If she clears her browsing data, switches phone or laptop, or uses a private window, the work is gone and there is no copy anywhere. Tell her to download the file before she closes the page, even if she has not finished — a part-done file converts perfectly well and she can carry on later.
They will not see each other’s answers, and whichever file arrives second is not a merge of the two. One outlet, one person.
Check the store total, never a single counter. Money keyed to the wrong counter nets out in the store total, so a counter being short does not on its own mean a sale is missing.
IDCP holds the ticket price in Unit Price and puts the discount in a separate
code — L10 is the 10% sale-period discount. So a garment ticketed at RM49.90
and sold for RM44.91 is keyed as 49.90 + L10, not as 44.91. The import already
does this. If you see the net price sitting in Unit Price with no code, the money is right and
the discount is wrong.
Tool and files: Dropbox\Claude\shared\MR_S\parkson-b2b-skill\RUN\
Finished packs: O:\Account\MONTHLY FIGURE\PARKSON\KH\