Picture the start of a new packaging job.
You need a contact panel: a small logo, an address, a website and a line of supporting text. You made a good one for another project. The spacing was right. The text styles were right. It should take a moment to reuse.
You open an old Illustrator file, find the group and copy it.
A colleague looks over.
“Is that the one with the updated icon?”
You are fairly sure it is. Then you open a second file to check.
The element already exists. What is missing is an easy way for the team to know which version to trust.
Three copies, three slightly different answers
Imagine comparing the contact panel in three recent jobs.
One has the newer icon. Another has better spacing around the address. The third has the wording the brand manager approved last month.
You combine the correct parts and check the result. The panel is ready, but the next colleague could still copy any of the older versions.
Before closing the file, give this panel a shared home.
The panel needs a few rules as well as a name
With the designer and the person preparing the automation, try a longer address. It pushes the website down. Decide whether the panel can grow and which gaps should stay the same. Write the answer in ordinary language:
“Keep the logo where it is. Let the address use another line. Move the website below it and keep the same gap.”
In Paqira, a snippet is a reusable set of instructions that creates an artwork element inside Illustrator. It can use the current product content and prepared design rules.
Someone builds and tests the snippet using the agreed rules. An operator can then insert the prepared panel without rebuilding it or making the same spacing decisions again. Colleagues use the same rules for spacing and alignment, so the result depends less on who happens to be preparing the file that day.
Two projects need two different kinds of copy
Now you need the panel in a standard label and a special campaign poster. The label should follow the shared version. The poster needs different styling for a one-off design.
A linked snippet stays connected to its source. It can be rebuilt when the snippet or preview data changes. In Paqira, refreshing it replaces the previous group in its existing position.
A snapshot inserts the current result as a fixed copy. Later changes to the shared snippet do not rebuild that copy.
You choose linked for the label and snapshot for the poster. Manual changes inside the linked panel may be replaced during a refresh. The poster keeps its local edits, but future corrections need separate attention.
The brand icon changes
A week later in this imagined job, the brand team supplies a revised icon. The snippet maintainer updates the shared version, and you refresh the linked panel in the label. You check the poster's fixed copy separately.
Updating the source does not change every saved or delivered file. The operator still needs to identify affected jobs, produce new results and check them. Try the panel in both a wide and a narrow layout before sending it on.
The difference is where the correction begins: one known source, with a clear route into each project.
Let a new colleague try it
Name the snippet “Product contact panel.” Add a short description of where to use it and who maintains it. Then ask someone outside the setup work to insert it.
Can they find it? Can they choose between linked and snapshot? Do they know what to check?
If they hesitate, improve the instructions before adding twenty more elements. Start with one panel that people repeatedly rebuild or copy incorrectly. A price badge or a specification table might come next.
On the next packaging job, you know where the panel came from and how updates will affect it. You can insert it, check it and return to the new design work without wondering whether you copied an outdated version.
See Paqira's guide to linked snippets and snapshots for the working details.