Quantity creates a question the SKU cannot answer
Two copies of a standard guide may require one shared download. Two personalized portraits may require two different finished files. The order can look similar in both cases, but the production obligation is different. Write down the unit-level requirement before choosing a delivery structure.
QuickAttach describes file or link association per order item. That is not documentation of a separate attachment slot for every unit in a quantity field. Do not sell a per-unit delivery experience based on that assumption.
Classify the quantity before production
| Two units mean | Deliverable requirement | Question to validate |
|---|---|---|
| Two uses of the same material | Potentially one identical file | Does the purchase promise require anything else? |
| Two distinct personalized outputs | Two identifiable outputs | Can they be associated separately or packaged clearly? |
| Two recipients | Recipient-specific access decision | Does the delivery method support that routing? |
The third case introduces a separate issue. Having two units does not prove there are two recipient email fields. Resolve recipient routing independently from the file count.
A fictional two-pet portrait order
Order 4204 contains “custom pet portrait,” quantity two. The accepted brief identifies a cat portrait and a dog portrait. The merchant’s manifest names both outputs and checks them against the brief. They then inspect the actual order-item controls rather than trying to attach one file and hoping a second unit will become visible.
If separate per-unit association is not supported, a combined package may be suitable when it matches the customer promise. Its contents should make the two portraits obvious. Another order structure may be appropriate for future sales, but changes to a live order need their own review.
A quantity acceptance protocol
- Create a synthetic order with one line and quantity two.
- Record how the app presents that line and which attachment controls exist.
- Prepare two harmless outputs with distinct markers.
- Try only documented or supported delivery structures.
- Inspect the recipient’s available downloads and their labels.
- Confirm that the customer can identify both outputs and that the delivery record remains understandable.
This is a proposed test, not evidence of per-unit support. If the needed relationship cannot be represented, contact QuickAttach support with the synthetic scenario. The right outcome is a confirmed delivery design, even when that requires changing how future custom products are offered.
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