Skip to content
eyeView Brands

The packaging catalog for your whole operation

Organize the portfolio by customer, brand, SKU and component. Every printed piece carries its own artwork, its own approval cycle and a single source of truth — from setup to the supplier's hands.

Structure

From brand to file, in a single hierarchy

Every level exists for a practical reason. You navigate top down and always land on the right file.

01

Brand

Your customer's brand, with logo, internal code, category and status.

02

Group

An optional level you name however you like: factory units, shelves or lines.

03

SKU

One specific pack, with GTIN, net content, variant, markets and languages.

04

Component

Each printed piece of the pack: label, carton, lid, insert.

05

Version

The file itself, with its lifecycle stage and full history.

The Group level is optional — SKUs without a group appear directly under the brand.

How it works

From brand setup to artwork in the supplier's hands

01

Create the brand

Every brand belongs to a customer. Set the logo, internal code, category and status — or bring the whole catalog in from a spreadsheet.

02

Structure the SKUs

Create SKUs with code, GTIN, net content, markets, languages and the custom fields your operation uses.

03

Link files to components

Each printed piece gets its own versions. The file stays in the Library — nothing is duplicated.

04

Approve, make current, publish

Current and Published are separate gates. Only approved work can go out to a supplier.

Features

Everything a packaging catalog needs to have

Folders that are saved searches

Catalog folders do not hold files — they filter. The file stays in the Library and can appear in several folders at once, with no copies.

  • No duplicated files across folders
  • Two folders can never drift out of sync
  • No risk of sending an old copy to the printer

Demo coming soon

Lifecycle per component

Label, carton and lid are printed by different suppliers on different lead times. Each one carries its own artwork and its own approval.

  • Stages: Draft, In review, Approved, Current and Obsolete
  • Ready-made types: front panel, back panel, label, carton, lid and insert
  • Version count visible on every component

Demo coming soon

Current and Published, kept apart

Every component carries two independent pointers. Only the current version can be published, and only what is published reaches the customer.

  • Approving a proof never publishes on its own
  • Unpublishing takes it down immediately

Demo coming soon

Supplier delivery with a real receipt

Send final artwork through an expiring link. Each recipient gets their own link, so the receipt is individual and honest.

  • Opened, downloaded and how many times, per person
  • Expiry from 7 to 90 days, revocable at any time
  • Suppliers do not need an account

Demo coming soon

Where this file is used

One file can serve several SKUs. Before you change anything, the catalog shows you the blast radius.

  • A "used in N places" badge on every file
  • A list of every affected version and SKU

Demo coming soon

Import and association assistant

Bring your current catalog in from CSV or Excel and let the assistant suggest links to the projects, folders and files you already have.

  • Preview before writing, with valid and invalid rows
  • Nothing is applied without your confirmation

Demo coming soon

Who it is for

Built for teams handling many packs at once

Brand owners

Centralize the whole portfolio by brand and SKU, using your own ERP code, and always know which artwork is live.

Agencies and prepress

Every brand belongs to a customer. Run several clients side by side without mixing files or permissions.

Converters and printers

Receive approved artwork only, through an expiring link, with a record of who opened it and who downloaded it.

Outcome

Less rework and fewer wrong files at the printer

A single source of truth

The file is stored once. There is no old copy circulating in another folder.

Suppliers get only what is approved

Only approved or current versions can be sent, and the link stops serving the moment you revoke it.

History that survives an audit

Nothing is deleted — everything is archived. Each change keeps the before and after, and survives archiving.

Frequently asked questions

Common questions about the brand and SKU catalog.

Which plan includes Brands?
Brands is part of the Enterprise plan. It also starts switched off and is enabled per organization — talk to us to turn it on for your account.
Do I have to duplicate files across folders?
No. Catalog folders are saved searches: the file is stored once in the Library and can appear in several folders at the same time.
Does approving a proof publish the artwork?
No. Approval marks the version as Approved. Making it current and publishing it are two separate steps that you take yourself.
Does the supplier need an account?
No. They receive their own link with an expiry date, and the download is recorded. You can revoke the link at any time.
Can I bring in the catalog I already have?
Yes. The import accepts CSV or Excel with customer, brand, product, SKU code and SKU name, and shows a preview with valid and invalid rows before writing anything.
eyeView logo

Join thousands of companies using eyeView.