Read the policy as two separate clocks
Joyagoo's current warehouse storage page describes one clock for individual items and another for a submitted parcel awaiting international-freight payment. The item clock begins when the order changes to Stored and currently carries a published 90-day free period. The parcel clock begins after parcel submission and before freight payment, with a published 30-day free period. Combining those rules into one vague 'warehouse deadline' can cause a buyer to watch the wrong event.
Treat every period as a policy snapshot checked on a particular date, not a permanent promise. Save the official wording and the live account record together. The help page explains the general rule; the warehouse or parcel screen shows which transaction, status and countdown are actually in front of the buyer. When the two do not align, preserve both and ask for clarification before the earlier defensible deadline.
Find the item-level trigger
The storage page says the free item period starts when the order status changes to 'Stored.' Joyagoo's separate order-status page uses 'Stored in Warehouse' for items that are stored and can be shipped during the free period. Record the exact label that appears in the account rather than forcing one page's capitalization or wording onto another. The important evidence is the transition into the stored state and its timestamp.
Seller dispatch, Stock Arrived and QC Completed belong to the item history, but they are not the storage trigger described on the current storage page. If the interface shows only a date, save the date, account locale and time zone and use a conservative internal deadline. Do not calculate from the purchase date or from another item that arrived in the same order group.
Give each stored item its own row
Items purchased together can arrive and become stored on different days. A late seller does not reset the clock of an earlier item, and a consolidation plan does not merge their histories. Build a ledger with order number, source listing, selected option, stored-status timestamp, published free-period end, displayed countdown, extension state and planned parcel group. Sort it by the earliest action deadline.
Use clear states: return decision open, keep confirmed, parcel planned, extension requested, parcel submitted or resolved. A vague note such as 'waiting for more items' hides the actual risk. The ledger should identify who owns the next action and when it must happen. That makes storage policy operational without turning it into a shipping-cost guide.
Calculate a defensible item deadline
For the currently published 90-day period, add 90 continuous days to the stored-status timestamp in the same time zone. Write both the calculated boundary and an earlier internal action date. The internal date should leave enough room to finish QC decisions, resolve a return question, select parcel contents and complete any necessary payment. It is a planning buffer, not an extension of the official period.
If a live countdown disagrees with the calculation, keep screenshots of the status, countdown and account time. Use the earlier boundary until the discrepancy is resolved. Do not announce that every calendar interpretation receives extra time. A defensible record states the source, date checked, arithmetic and uncertainty so that support can answer the transaction-specific question.
Document an extension as a new policy event
The storage page currently says an item extension costs 10 CNY for 30 days through 'Extend Storage.' That is a dated published term, not authority to assume the button, price or duration will always appear for every item. Before relying on it, open the exact warehouse record and save the option label, amount, currency, extension length and eligibility shown at that moment.
After payment, preserve the receipt, transaction time, affected order number and new displayed expiry. Do not infer success merely because the balance changed. Check that the extension attached to the intended item and that the deadline moved as expected. If several items need more time, verify each one separately; one extension record should not silently stand in for an entire parcel group.
Do not confuse return and storage deadlines
The QC return clock and warehouse storage clock answer different questions. The current return policy links the ordinary request window for eligible items to QC Completed, while the storage page starts free item storage at Stored. A long storage period does not reopen an expired return opportunity. Equally, an unresolved return should not be treated as a confirmed item ready for consolidation.
Keep both timestamps in the item row. Close the keep-or-return decision first, then decide whether to ship, wait or extend storage. If a return or exchange is still being negotiated, save the status and support instructions instead of assuming the storage clock pauses. Only a transaction-specific display or written answer can establish that effect.
Start a new row when a parcel is submitted
Once items are submitted as a parcel but international freight remains unpaid, the current storage page describes a separate 30-day free parcel-storage period. Record parcel number, included item numbers, submission timestamp, freight-status label, displayed amount, payment deadline and any cancellation or recalculation state. Do not carry the oldest item's 90-day calculation forward as if it controlled the submitted parcel.
The published order-status list includes Parcel Waiting to Pay and also says that a calculated shipping fee may require payment within a shorter displayed period. This means a buyer should not use the general 30-day parcel-storage period to ignore a transaction-specific payment instruction. Save both rules, follow the earlier active deadline and ask when the account presents an unresolved conflict.
Treat abandonment language as a stop signal
The current storage page states that goods may be treated as abandoned and destroyed when the relevant item or parcel period is exceeded without parcel submission, freight payment or communication. That is a serious consequence, but this guide should not guess the exact disposal moment for an individual case. The defensible response is to act before expiry and preserve evidence of any communication.
A last-minute message is not a guaranteed extension. Record the channel, timestamp, order or parcel number, question and reply. If payment or submission cannot be completed, request written transaction-specific instructions while the period remains open. Never advise a buyer to test the boundary by waiting for a warning notification that the published page does not promise.
Run a weekly exception review
Review the ledger at least weekly and filter for items with the earliest internal dates, missing stored timestamps, unresolved QC decisions, unconfirmed extensions and submitted parcels awaiting payment. Check the live account rather than merely reducing a number in a spreadsheet. A status change, extension receipt or parcel cancellation must become a new dated entry, preserving the older evidence instead of overwriting it.
Use red, amber and green as workflow labels, not risk guarantees. Red means action is due before the next review; amber means a required fact or confirmation is missing; green means the next action is scheduled with adequate evidence. Even a green item retains its original deadline and source because future seller, warehouse or parcel events can change the plan.
Close with an auditable expiry-prevention record
A complete record contains item or parcel identity, controlling status, trigger timestamp, time zone, published policy version, calculated boundary, earlier internal deadline, live countdown, extension option, receipt, communication and final resolution. Save only necessary transaction evidence and exclude private address or payment credentials from any shared copy. The record should let another person explain every date without inventing a policy.
The practical conclusion is narrow: separate item storage from parcel storage, calculate from the stated trigger and never let consolidation plans conceal the oldest deadline. Joyagoo's current published terms provide usable baselines—90 days for stored items, an optional 30-day item extension at 10 CNY, and 30 days for a submitted unpaid parcel—but buyers should recheck the live rule and their account before relying on any number.
