Start with relationships, not directory names
Shared folders often mix source material, drafts, exports, and delivered versions. A customer may have several purchases in the same directory. Preserve the existing structure during discovery and record which file was actually approved for delivery.
Choose one owner for each ambiguous folder. If the team cannot establish a file-to-order match from the order and production record, leave it unresolved. Similar names, modification dates, and the newest filename are clues, not sufficient proof.
A practical inventory template
| Field | Synthetic example | Purpose |
|---|---|---|
| Source reference | project-cedar/export-02 | Locate the controlled original. |
| Order and item | DEMO-482 / review | Identify the intended purchase. |
| File role | Approved final | Exclude drafts and source inputs. |
| Revision | R2 | Distinguish corrected work. |
| Access owner | Delivery team | Keep external permissions maintainable. |
| Disposition | Ready / hold / exclude | Control the migration batch. |
Store this register in an approved internal location. Avoid copying customer documents or personal details into a spreadsheet simply to make the migration convenient.
A fictional folder that needs splitting
The folder cedar-project contains an initial report, a later update, and working notes. The first two belong to different purchases. The working notes were never sold. The team records two order associations and excludes the notes rather than uploading the whole folder as one customer package.
If the intended deliverable is a folder link, review every visible file and inherited permission. A private-looking folder name does not establish restricted access, and linking a folder from an app does not copy or isolate its contents.
Transfer only verified finals
QuickAttach’s documented workflow attaches a file or link from an order. It does not imply that an existing shared-drive directory can be imported automatically with its relationships intact. Move a small verified set, then check the customer-facing route and the support lookup.
- Confirm the approved revision opens.
- Check order and item independently.
- Choose uploaded copy or maintained external link.
- Test access through the intended delivery path.
- Mark the inventory row completed with a date and owner.
Keep unresolved files outside the send queue. Completion counts should distinguish transferred files from verified deliveries; otherwise a successful upload can conceal a wrong association.
Deliver the right file with the right order
See how QuickAttach connects a customer-specific file or link to a Shopify order item.
See the QuickAttach order-to-download walkthrough