A workflow with one deadline and one lane

The return-window countdown

Each product carries a return-by date, defaulted from your purchase date and always editable — windows vary by category and promotion, so the number the tool guesses is a starting point, not a rule.

Everything still unfilmed shows how many days are left, calculated in your own timezone rather than UTC, because a return window that expires "tomorrow" needs to mean tomorrow where you live. Ten days out the badge turns amber. Five days out it turns red. Past the date it goes grey and says the window has closed, which is information you still want — that product is now a keep, whether you meant it to be or not.

A queue you are not allowed to reorder

Products in hand and not yet started sit in one column, sorted by return date, then by cost descending, then by age. The top card is the next thing to film. There is no drag handle in that column and that is the feature: the moment you can reorder the queue, you reorder it toward the thing you feel like filming, which is how the expensive item on a five-day clock ends up at the bottom.

One product at a time, enforced

Scripting, recording, editing and ready-to-upload are collectively one card wide. Moving a second product into any of them is refused, and the refusal names the card that is blocking it and offers to park that card back in the queue so you can swap in one click.

Review and published are unlimited, because moderation latency is not yours to control and waiting on it must never stop you starting the next video.

Rework is a first-class path

A rejected video goes back to recording or editing with the reason recorded against it, and the rejection count travels with the product. You can also withdraw something you have already submitted — you watched it back and spotted the problem before the moderator did — without throwing the work away.

A cost ledger that fills itself in

Cost and purchase date are captured when the product goes on the board. When a video goes live or a product is abandoned, SendShelf asks the one question that makes the ledger usable: did you keep it or return it, and on what date. The answer is required, so the ledger cannot quietly develop holes.

The result is a running list of what you spent, what came back, and what each published video actually cost you in product.

A library as a by-product

A video only counts as published once it has a URL and a publication date, which means the list of what you have made is complete and correct without anyone maintaining it. Every state change is recorded with a timestamp from the first day, so how long things actually take is a question you will be able to answer later.

What it deliberately does not do

• It does not connect to Amazon. No scraping, no Creator Hub access, no stored Amazon credentials — see the note on the home page for why that is a decision rather than a gap.
• It does not import earnings, and it does not tell you what a video made.
• It does not edit, host or upload video.
• It is a desktop and tablet tool. It is designed for the machine you edit on, not for a phone.

It is built for creators in the Amazon Influencer Program, and it does the part of that work that nothing else is watching.