Contacts, PR projects and Mintsoft exports — marketing builds, operations ships
Excel (.xlsx / .xls) or CSV. Drop it in and the portal maps the columns, formats the addresses, finds the SKUs and builds the file. It only stops if something genuinely can't be resolved.
Auto-detected where possible. Only Name, Address and Products are required.
First 5 rows as read from the file.
Click a row to open it. Red = must fix before export. Amber = worth a look. Learned SKU matches are remembered for next time.
Mintsoft MultiLineOrderTemplate schema — one row per SKU per recipient.
Every SKU in Shopify, pulled live through the Worker. The Admin API token stays on the Worker and never reaches this page.
Which statuses can be matched and picked:
Every manual SKU pick you make is saved here, so the same wording matches automatically next time.
Applied to every order in the batch.
Must match your Mintsoft dropdown exactly.
Builds PREFIX-INITIALS-001
Points at the Worker that holds the Shopify Admin token. Reuses the same custom app as the Staff Ordering Portal — read_products is the only scope it needs.
Pre-filled. Clear it to fall back to the built-in default.
No trailing slash. https:// is added if you leave it off. The portal calls /api/catalogue on it.
Full auto still stops if a SKU or address can't be resolved.
Worth knowing when someone else opens the portal, or you use a different browser.
| Data | Stored | Shared? |
|---|---|---|
| Contacts | Database | yes — whole team |
| PR projects & giveaways | Database | yes — whole team |
| Shopify catalogue | Re-synced per browser | same data |
| Learned SKU matches | This browser | no |
| Settings on this tab | This browser | no |
Everyone needs the portal password to see contacts and projects.
For placeholder addresses like "Skin Cupid Office" that appear in PR lists instead of a real address. One per line: Label | Addr1 | Addr2 | Town | Postcode
Marketing builds the list and hits Finalise; operations picks it up, fixes anything that needs fixing, and exports to Mintsoft.
Got the PR list as a spreadsheet? Drop it here and it'll pull out the people, addresses and products and add them straight into this project.
What everyone gets by default. Add it here once, then override per person below if shades differ.
Only people marked accepted go into the Mintsoft file.
When the list is settled and you've heard back from everyone you're going to hear back from, finalise it. Operations picks it up from there — nothing is locked, so you can still make changes if something lands late.