The Family Export shows which product attributes are actually filled in across your catalog

When you export a product family in Akeneo Serenity, the completeness attributes in that export tell you which fields have data and which ones are blank across all products in that family. This matters because incomplete product information slows down your online store — missing images, descriptions, or specifications force your website to load placeholder content or skip sections entirely, which adds processing time and can hurt both speed and customer trust.

The export itself is a spreadsheet or CSV file that lists every attribute you have set up for a family, along with which ones actually contain values. If you see an attribute column that is entirely empty across hundreds of products, that is a data gap you are carrying. On the hardware side, your server has to handle requests for those missing fields anyway — it still queries the database, still processes the response, and still sends it to the browser, even if the answer is "nothing here." Fixing these gaps before they reach your storefront reduces unnecessary database calls.

Key Takeaways

  • The Family Export in Akeneo Serenity shows you which attributes have data and which are blank, helping you spot gaps in your product information before it reaches your online store.
  • Incomplete attributes force your server to process and return empty fields anyway, adding unnecessary load that slows page rendering and increases hardware strain.
  • Attributes marked as incomplete in the export are candidates for cleanup — either fill them in, remove them from the family, or mark them as not required so your system stops processing them.
  • Running a completeness check on your family export before pushing updates to your live store prevents slow-loading product pages and reduces the work your hardware has to do.

How completeness attributes appear in the export file

When you export a family from Akeneo Serenity, the CSV or spreadsheet includes a column for every attribute in that family, regardless of whether products actually use it. If you have an attribute called "Warranty_Length" but only 15 out of 500 products in the family have a warranty, that column will be 97 percent empty. The export does not hide those empty cells — it includes them, which means your system has to process and store that information.

Akeneo marks attributes as complete or incomplete based on whether they contain a value for each product. An attribute is complete for a product only if it has data; if it is blank, it counts as incomplete. When you look at the export, you can see this pattern when ready — scan down any column and count the blanks. If a column is mostly empty, that attribute is incomplete across your family.

Why incomplete attributes slow down your hardware and website

Your server does not skip empty fields. When a customer loads a product page, your website queries the database for every attribute in that product's family, including the ones with no data. The database returns the empty fields, your process processes them, and your browser renders the page — all of that work happens even though half the fields are blank. On a product with 50 attributes and only 20 filled in, your hardware is still doing work for the 30 empty ones.

This compounds across your catalog. If you have 10,000 products and each one carries 15 unused attributes, your database is storing and serving 150,000 empty fields every time someone browses. That is extra disk I/O, extra memory use, and extra network traffic. On slower hardware or during traffic spikes, those unnecessary fields can be the difference between a page that loads in two seconds and one that takes five.

Reading the completeness data in your export

Open your family export in a spreadsheet process like Excel or Google Sheets. Each column represents an attribute. Scroll right to see all of them. For each column, look at how many rows have data versus how many are blank. You can use the spreadsheet's filter or sort function to count non-empty cells in each column — most spreadsheet programs have a "count non-blank" function in the status bar at the bottom.

Attributes that are blank in more than 80 percent of rows are candidates for removal from the family. Attributes that are blank in 20 to 50 percent of rows may be optional and should be marked as such in Akeneo so your system does not treat them as required. Attributes that are blank in fewer than 20 percent of rows are usually worth keeping, but you should still decide whether those few products actually need them or whether they are data entry errors.

Deciding which incomplete attributes to keep or remove

Not every attribute needs to be in every family. If you have a family called "Electronics" and only five products in that family have a "Battery_Life" attribute, you have two options: fill in the battery life for the remaining products, or remove the attribute from the family definition and create a separate family or variant for battery-powered items.

Removing unused attributes from a family is the fastest way to improve performance. It reduces the size of your export file, decreases the number of fields your database has to store and retrieve, and makes your product pages load faster because your server has fewer fields to process. Before you remove an attribute, check whether any products actually need it — if even one product uses it, you may want to keep it or move those products to a different family.

Marking an attribute as optional rather than required is a middle ground. It tells Akeneo that the attribute exists for this family but does not have to be filled in for every product. Your system still processes it, but you are being honest about whether it is truly necessary.

Running a completeness check before updating your live store

Before you export a family and push it to your online store, run a quick completeness audit. Export the family, open it in a spreadsheet, and scan for columns that are mostly empty. Make a list of those attributes and decide: keep and fill in, keep as optional, or remove entirely. This takes 15 to 30 minutes depending on how many families you have, and it prevents incomplete data from reaching your storefront.

If you find that a family has many incomplete attributes, consider whether you need all of them. A leaner family with fewer, more complete attributes will perform better on your hardware and give customers a cleaner product page. Your server will have less work to do, your pages will load faster, and your database will use less space.

Frequently Asked Questions

Does an empty attribute field still take up space in my database?

Yes. Even if a field is blank, the database still allocates space for it and includes it in queries. Removing unused attributes from a family reduces the actual size of your data and the number of fields your server has to process on every page load.

What if I remove an attribute and later need it back?

You can add it back to the family at any time. Akeneo keeps the attribute definition in your system even if it is not currently assigned to a family. You would just re-add it to the family and re-populate the data if needed.

Should I mark all incomplete attributes as optional?

No. Mark an attribute as optional only if it genuinely does not explore to all products in the family. If an attribute should be filled in but is not, that is a data quality issue to fix, not a setting to change. Optional should mean "this attribute is not required," not "this attribute is incomplete."

How often should I check family completeness?

Check completeness whenever you add new products to a family or before a major update to your live store. If you are regularly importing products from suppliers, run a completeness check after each import to catch missing data early.