The shop portal is for retailers. It collects the pull lists of every customer who has connected to your shop, so you can see what to pull this week and what to order, without keeping it on paper.
The portal needs the Shop plan. Claiming a shop profile is free, so you can see who is waiting for you before you decide to pay.
Getting your shop set up
There are two ways in.
- A customer invited you. Open their link, create an account, and claim the shop. Any customers who already added your shop appear immediately.
- You are starting from scratch. Create a shop in the portal and share your details so customers can find you.
Customers
A customer connects to you from their side. Requests arrive as pending until you approve them. You can add private notes to a customer record, pause someone who is travelling, or remove them. Notes are yours; the customer does not see them.
The weekly view
This is the working screen. Pick a week and you get every release your customers expect, grouped so you can work down the list. Each one moves through three states:
- Pulled — you have set it aside.
- Available — it is ready, and the customer is told.
- Skipped — you could not get it, or they passed.
Ordering
The aggregate view answers the only question that matters when you place an order: across all customers, how many copies of each book do I need. It totals the same week’s releases into one list per title.
You can export that list in three shapes:
- Diamond order form CSV
- Lunar and PRH spreadsheet layout
- A generic CSV with title, issue, publisher, UPC and quantity
Printing
Pull sheets print per customer or per week. Print at 100% with scaling turned off. See browsers and devices if the output looks wrong.
Connecting your own systems
If you run a point of sale or inventory system, the shop API lets it read customer lists and releases and write status changes back. You generate a key in the portal, and it is shown once. Webhooks can push events to you as they happen rather than you polling for them.
Gotchas
- Customers own their lists. You can mark releases and add notes, but you cannot edit what somebody has asked for. That is deliberate.
- Releases come from your customers. There is no automatic feed of upcoming issues, so the weekly view reflects what has been entered.
- Marking something available notifies the customer. Use pulled while it is still on your shelf.
- An API key is shown once. If you lose it, generate a new one, which immediately stops the old one working.