This is an audit-readiness view of what VaultLabs publishes: which artefacts a UAE laboratory can put into its own quality file, what each one evidences, and where the supplier's responsibility ends and yours begins. It is deliberately not a description of what happens inside a manufacturer's laboratory. When an auditor asks how you qualified an incoming lot, the answer has to be built from documents you hold, not from a supplier's assurances.
What the framework gives you to file
Four things are usable in an audit file. Per-lot analytical records, where they have been uploaded, are reachable through the COA portal. A lot lookup exists so the identifier on a vial can be checked against a published record through batch verification. Pricing and checkout are handled in AED, so purchase documents and receiving records share one currency. Dispatch covers the seven emirates, which means the transit leg is a described part of the order rather than an unknown.
Everything else in your file is your own work: the receiving log, the acceptance criteria, the release decision, the inventory row. That division is worth stating explicitly in your SOP, because auditors ask about the boundary more often than about either side of it.
The per-lot record is the load-bearing artefact
A supplier's general quality description cannot be filed against a vial. A per-lot record can. This is why the practical centre of the framework is the lot identifier: it is the key that joins the physical unit, the analytical document, and your inventory row into one traceable object.
Regard the published record as a reference layer rather than a release decision. It reports what was measured on that lot. Whether the lot meets your requirements is a determination only your laboratory can make, and the file should show that you made it.