How to record packing video proof on Shopify

Search for a packing video app for WooCommerce and you find almost nothing. Search for one for Shopify and you find a dozen, which is a different problem: the listings describe the same surface in the same words. Record the order. Add a watermark. Share a link. Read four of them and you still cannot tell what you would actually be buying.

The way out is to stop reading feature lists and ask what happens at the two moments that matter — the moment a support agent opens the order, and the moment someone who does not trust you looks at the file. The category itself, and why a recording is not the same thing as proof, is covered in packing video proof; this piece is the Shopify half of it.

The recording is the easy part

Any phone can film a box being packed. Nothing about the capture is hard, and no app is meaningfully better at it than another. What separates these tools is everything that happens after the file exists.

A recording becomes evidence when two questions have answers a stranger can check:

Which order does this belong to? Not according to you — according to something that cannot be typed in afterwards. A filename is not an answer. A folder named after the order is not an answer. The order reference has to be in the picture, and the file has to be bound to the order in a system that records when that binding was made.

Has it been changed since? Not "we promise it hasn't". A fingerprint taken from the exact bytes that arrived, so that altering a single frame produces a different fingerprint and the file no longer matches the sealed record. A watermark makes a file identifiable; it does not tell anyone whether the file was edited.

Everything below is about getting Shopify to carry those two answers for you.

Where the proof has to end up

This is the question most Shopify packing video apps answer badly, and it is the one that costs you money.

Picture the moment the evidence is actually needed. It is not you, at your desk, with the app open. It is a support agent working a ticket at 9pm who has never heard of the tool you bought. It is a bank reviewing a dispute you will never speak to. It is you in four months, trying to remember which of last spring's orders is being argued about.

All three of those people start in the same place: the Shopify order. If the recording lives only in a third-party dashboard, the agent has to know it exists, know which app, have a login, and go looking. Most of the time they do not, so they answer the ticket without it, and the recording you paid to make has no effect on the outcome.

On Shopify the fix is unglamorous and specific. The proof link goes onto the order in three places:

• An order metafield, which is the structured, machine-readable home for it.
• An order tag, so orders with proof are filterable in admin and in exports.
• An order note, because that is the field a human actually reads first.

Written that way, someone who has never heard of PallasMark can open the order, see a link, click it, and get a page that tells them whether the recording is sealed and when it was made. No account, no explanation, no training.

The Shopify-specific part: bind the proof to the line item

This is the thing Shopify lets you do that most platforms do not, and it is worth setting up properly.

Shopify's order payload gives you the line item id together with the product id and the variant id. That means a recording can be bound to one specific line rather than to the order as a whole.

It matters on multi-item orders, which is most of them once your average order value climbs. A buyer disputes one item out of five. If your proof is attached to the order, you are handing over a video of five things being packed and asking a reviewer to find the relevant three seconds. If it is bound to the line, you are answering the claim that was actually made.

It also matters for variants. "You sent the wrong size" is an identity claim about a specific variant, and a proof that knows which variant it shows is a direct answer rather than a general one.

Connect through the App Store, not with pasted keys

Some tools in this category ask you to create an Admin API access token and paste it into their form. It works, and it is a bad habit.

An App Store install is OAuth: the scopes are shown to you before you approve them, the grant is recorded, and you can revoke it from your admin without contacting anyone. A pasted token is a long-lived credential sitting in a third party's database that you now have to remember to rotate, and that you cannot revoke selectively.

There is a second reason on the receiving side. Order webhooks should be verified by HMAC signature before anything is trusted, with the store identified from the signed header rather than from the request body — a body can be spoofed, a signature cannot. If a tool is casual about how it connects, that is usually a signal about how it handles the rest.

Fulfillment holds: useful, but do not build on them

A fulfillment hold pauses dispatch until something happens — in this case, until the buyer confirms what they are about to receive. For high-value or high-risk orders it is genuinely useful: the confirmation happens before the parcel leaves, so a later "that is not what I ordered" has an answer the buyer already agreed to.

The honest caveat, which you will not find in most app listings: Shopify only holds fulfillment orders that are still interruptible. If the fulfillment order has already moved on, or if none exists yet for that order, the API refuses and no app can force it. In practice that means holds work well for orders that sit briefly before dispatch and not at all for stores that fulfill the moment payment clears.

Treat holds as a bonus on the orders where they apply. If your process depends on every order being holdable, you will find out the hard way which ones are not.

What not to do: Shopify Files

The tempting shortcut is to upload the clip to Shopify Files and link it from the order note. It puts the video near the order, it costs nothing, and it takes a minute.

It also gives you a file on a public CDN URL with no access control, which anyone holding the link can watch — including the buyer you are in a dispute with, and anyone they forward it to. And it gives you no binding between the file and the order beyond whatever you typed into the filename. A filename can be written after the fact, which is precisely why it proves nothing.

Shopify Files is the right place for product images. It is the wrong place for evidence.

Filming it, in practice

The recording itself should be boring and identical every time. That is the point — a routine that varies is a routine that gets skipped under pressure.

1. Start with the empty box in frame. The claim you are answering later is usually about what was or was not in it.
2. Show the item and its condition before it goes in. Turn it so the parts that get disputed are visible: the screen, the seam, the seal, the serial.
3. Get the order reference in the picture. The packing slip, the label, a screen — anything that is in the shot rather than in the metadata.
4. Tape the box on camera. The transition from open to sealed is what makes the recording cover the whole question.
5. End on the readable shipping label. That is what ties the parcel in your hand to the tracking number in the dispute.

One take. No cuts. A cut is a place where a reviewer can imagine something happening off camera, and you cannot argue them out of it afterwards.

Making it something the team actually does

A process that depends on remembering does not survive a busy week.

Put the recording where the packing already happens — the order open on the phone or laptop at the bench, not a separate app someone has to think about. Decide up front which orders get filmed: everything, or above a value threshold, or specific SKUs with a history of claims. Deciding once is what stops it becoming a judgement call at three in the afternoon.

And check the tag. If proofs are being written back as an order tag, you can filter Shopify admin for orders without it and see, in seconds, whether the routine is actually being followed. A process you cannot audit is a process you are assuming.

What it is worth when a dispute lands

For item-based disputes — wrong product, damaged, not as described — a sealed recording of the correct item going into the box is the documentation the card networks ask for. Visa's guidance for that dispute condition asks the merchant to provide as much specific documentation as possible and to address each point the cardholder raised, which is exactly what a recording bound to the disputed line item does.

It is worth being precise about the limit. A packing video does not answer "I never received it". That is a delivery question, and the answer is carrier proof of delivery. Anyone selling you packing video as a cure for every chargeback is overclaiming, and the overclaim is easy to check.

Where it pays off earliest is not the chargeback at all. It is the refund request that arrives weeks before a bank is involved, where you can send a verify link with your first reply instead of arguing — proof for refund claims and return abuse covers what that changes in practice.

Setting it up on your store

If you want the version of this that writes back to the order, binds to the line item and seals the file, that is what the Shopify integration does, and there is a free plan to test it on real orders before deciding anything.

If you are still choosing between tools, packing video software compared goes through what each one actually records, with every claim checked against the vendor's own page. And if you want the underlying practice rather than the platform wiring, the seven-point packing video checklist is the shorter read.