You can collect artwork for print orders in Airtable by linking each upload to the specific order line it belongs to, then recording a separate staff preflight decision. miniExtensions gives customers a place to submit files and read feedback, while your production team decides whether a particular version is ready for the printing process.

The essential distinction is between receiving a file and accepting it for production. An upload form can collect a document successfully even when the artwork has the wrong dimensions, missing content, or an unsuitable export. This workflow keeps those decisions visible instead of treating the presence of an attachment as approval.

Start with an order that needs more than one file

Consider a fictional print shop, Fieldstone Print, preparing a customer order containing two items: 200 folded leaflets and one outdoor banner. The customer submits a leaflet PDF and a banner file. The leaflet passes staff review, but the banner needs a revised export.

If both attachments sit on the order record, “Artwork approved” is ambiguous. Does it apply to both items or only the leaflet? Create separate order lines and separate artwork submission records so the production team can name the accepted version for each item.

This proposed design builds on the file upload and document portal tutorial, adding item-level identity, retained versions, and an explicit production handoff.

Create the Airtable records around the print job

Use a connected Airtable base and fictional samples:

  • Contacts: Name (single line text, primary field), Email (email), and Active (checkbox). One record represents one person who can log in.
  • Orders: Order Reference (single line text), Contact (linked record to Contacts), Requested Date (date), and Internal Job Notes (long text).
  • Order Lines: Item Reference (single line text), Order (linked record to Orders), Contact (linked record to Contacts), Product Description (long text), Quantity (number), Artwork Requirements (long text), Artwork Status (single select: Requested, In review, Revision needed, Accepted), and Accepted Artwork (linked record to Artwork Submissions).
  • Artwork Submissions: Submission Reference (single line text), Contact (linked record to Contacts), Order Line (linked record to Order Lines), Artwork File (attachment), Customer Note (long text), Created At (created time), Review Decision (single select: Pending, Revision needed, Accepted, Superseded), Customer Feedback (long text), and Staff Preflight Notes (long text).

The direct Contact fields are intentional. Order Lines and Artwork Submissions are portal-facing tables, so each needs the user relationship described in the users-table documentation. An order number or a contact lookup is not interchangeable with that linked-record field.

Name the two sample lines “FP-1042 — Folded leaflet” and “FP-1042 — Outdoor banner.” Put the actual requirements for each job in Artwork Requirements. The printing team should supply those requirements from its production process; this article does not prescribe universal bleed, color, resolution, or export specifications.

Give the customer context before the upload

Create the Portal from Order Lines and its Contact user field, then add Artwork Submissions. Configure login, user-specific views, and the child forms using the document portal tutorial. Keep order references, product descriptions, requirements, status, and customer feedback read-only. Do not let a customer change quantities, production specifications, or staff review decisions through the artwork form.

For new submissions, expose the appropriate Order Line selector, Artwork File, and Customer Note. Restrict the selector to the customer’s relevant lines and test that it cannot offer another customer’s work. Do not publish a broad dropdown of every order in the base. Verify that a saved submission links to both the intended customer and the correct line.

Keep Staff Preflight Notes out of the customer form. Use Customer Feedback for an actionable explanation such as “Please resend the banner artwork using the dimensions listed above.” Internal production discussion and customer-facing instructions serve different purposes and should not share one editable field.

For login, open Users & Login, select the email login field, and enable Two-Factor Authentication (Email verification). Use one valid email per user record.

For every private table view, open Views → Filter and Sort and set Choose Records to Display to Personal records only (linked to the logged in user). Repeat the two-user access check after adding views.

Configure the Order Line linked field in the create child form: open Filter Records and use Choose Records to Display to limit the finder to personal records. The destination table must link directly to Contacts. Turn off creation and expansion of destination records in that field so the selector cannot become another editing route. This documented personal-record finder filter does not change existing linked values; inspect those separately. Set Allow users to link to Single Record in Advanced, following the single-record selection guide.

Set upload rules without promising preflight validation

Choose a simple submission contract, such as one principal production file per artwork submission. The Maximum allowed files setting can enforce an attachment count. The documented Attachment Size Limit setting is in the attachment field’s Upload section and uses megabytes.

Choose limits that match files your team can receive and review, and state the accepted format in the instructions. These controls do not inspect fonts, color profiles, bleed, image quality, or print suitability. Staff still needs the appropriate preflight tools and production knowledge. A file that passes the upload rules may still require correction.

Keep earlier submissions read-only after they are sent and collect revisions as new records. The expanding form can display the old file, date, customer note, and feedback without allowing replacement. Check other portal views and linked-record forms too; one read-only view does not establish that every path is read-only.

Move each item through a separate review decision

Receive and identify the submission

The customer uploads the leaflet file against the leaflet order line. Staff checks that it is attached to the intended line and changes that line to In review. In this initial version, staff manages statuses manually. Adding an attachment does not automatically notify the shop, reserve press time, or establish a delivery commitment.

Record what production actually checked

A production reviewer examines the submitted file using the shop’s normal process. If it meets the job’s requirements, the reviewer marks that submission Accepted and links it in the order line’s Accepted Artwork field. Staff then sets Artwork Status to Accepted. This creates an explicit pointer to the file production is meant to use.

For the banner, the reviewer instead chooses Revision needed and writes a specific customer instruction. The order remains partly ready: the leaflet has an accepted version and the banner does not. This is more useful than moving the entire order backward or forward with one ambiguous status.

Review a replacement without erasing the earlier result

The customer sends a second banner submission. Its note can say what changed, but staff must inspect the file rather than accept the explanation as proof. Once accepted, link this exact submission on the banner order line. Retain the first banner record with its original feedback and label it Superseded when appropriate.

A later upload should not automatically replace Accepted Artwork. For example, a customer might submit a new file after the job has entered production. Staff should determine whether the change can be considered and communicate any implications through the normal order process. This workflow does not authorize changes in price, schedule, or contractual scope.

Make the production handoff explicit

Create an internal Airtable view of order lines with Accepted Artwork populated and Artwork Status set to Accepted. Before using that view operationally, have staff check that the linked submission also has an Accepted review decision. These are human-maintained fields in the first version; an inconsistent combination needs investigation, not silent assumptions.

The production handoff should include the order line reference, its requirements, and the accepted submission reference. If staff downloads files into another production system, preserve that identity in the handoff. A folder full of documents named “final.pdf” makes it too easy to use the wrong version.

Test the exception cases with fictional files

  • Create two sample customers and verify their portal views and order-line selectors independently.
  • Upload a sample file, save, reload, and inspect its exact customer and order-line relationships in Airtable.
  • Try a file above the configured size limit and a submission exceeding the allowed count; verify the actual response.
  • Record revision feedback, submit a second version, and confirm the first remains unchanged.
  • Accept one line while another remains Revision needed. Confirm the production view does not imply the entire order is ready.
  • Submit a later file and verify that Accepted Artwork does not change without the intended staff decision.

Keep the system’s role clear

This approach fits a small print team that needs organized collection and review alongside its existing production tools. It is not automatic PDF preflight, color management, proof approval, or a print management suite. Professional review remains separate.

The useful result is traceability at the item level: the shop can identify what was submitted, why a revision was requested, which exact file was accepted, and which item is still waiting before production proceeds.