A Pimcore Data Object<\/strong><\/a> is one record built from that blueprint. Think of the class as the mold and the object as a single casting.<\/p>\n Classes and data objects are how Pimcore models structured product and master data. This is the heart of Pimcore as a PIM.<\/p>\n You need no OOP knowledge. Pimcore turns the whole thing into a point-and-click job inside Studio.<\/p>\n Behind the scenes, Pimcore stores each Pimcore Data Object in MySQL. The visual editor writes that schema for you.<\/p>\n Get these ready before you start:<\/p>\n One important note. The legacy ExtJS “classic” admin panel no longer ships in Pimcore 2026.1.<\/p>\n So the old route “Settings > Data Objects > Classes” is dead. Everything now lives in Studio, and this post follows that path.<\/p>\n On Pimcore versions before Studio became the default, screens differ. This guide targets 2026.1, where Studio is the only admin UI.<\/p>\n Sign in to Pimcore Studio first. Then use the left navigation to reach the class list.<\/p>\n Follow this path exactly:<\/p>\n We will use the plain Classes<\/strong> editor here. That is where every Pimcore Data Object structure begins.<\/p>\n On the Classes<\/strong> page, click the add action to start a new class. Pimcore then opens a dialog titled Create New Class Definition<\/strong>.<\/p>\n The dialog gives you two inputs:<\/p>\n Respect the class-name rule. Studio states it plainly: “The class name must start with a letter and can contain only letters, numbers, and underscores.”<\/p>\n Mind the unique identifier too. Studio warns: “Be careful with the unique identifier because table names can contain only up to 64 characters.”<\/p>\n That 64-character limit is a real database constraint. Keep the identifier short so your table names never exceed it.<\/p>\n For our worked example, name the class When the editor opens, you land on the General<\/strong> tab. Review it first, then switch to the field builder to shape your object.<\/p>\n The General<\/strong> tab shapes how the class behaves overall. A first-timer only needs a handful of these fields.<\/p>\n Worth a look are PHP Class Name, Group, and Icon. Toggle Allow Inheritance, Allow Variants, and Show Variants only when your model needs them.<\/p>\n The tab also lists advanced settings. Description, ID, Parent Class, Implements Interfaces, Use Traits, and the generator references are safe to ignore for now.<\/p>\n For a simple The class editor is where you build the field tree. Pimcore gives you two add-actions, and both matter.<\/p>\n Click Add Layout Component<\/strong> to organize how fields appear in the object editor. This group controls tabs, panels, and fieldsets, not stored data.<\/p>\n The Layout Component<\/strong> group offers Panel, Tab Panel, Region, Accordion, Fieldset, and Localized Fields. Reach for a Fieldset to group related inputs visually.<\/p>\n Click Add Data Component<\/strong> to add the actual data fields. This is where each Pimcore Data Object gets its real values.<\/p>\n Pimcore groups the Data Component<\/strong> types into ten families: Text, Numeric, Date, Select, Media, Relation, Geographic, CRM, Structured, and Other.<\/p>\n Try the first field now. Click Add Data Component<\/strong>, open the Text<\/strong> group, choose Input<\/strong>, then set the field name to Repeat that pattern for each remaining field. Build the Each field name follows the same rule as the class name. Start with a letter, then use letters, numbers, or underscores only.<\/p>\n You should now see six data fields sitting in the tree. That is your full Relations deserve a mention. Under the Relation<\/strong> group, Many-to-One and Many-to-Many object relations link one Pimcore Data Object to another.<\/p>\n Structured items live under the Structured<\/strong> group. These include Field Collections, Object Bricks, Localized Fields, and Classification Store.<\/p>\n You might expect these two add-actions to need separate deep-dives. In Studio they are just the two buttons above, so you have both covered here.<\/p>\n Use the Save action in the class editor once the field tree looks right. This single action does two big things automatically.<\/p>\n First, Pimcore generates the underlying database schema. It creates the per-class MySQL tables that will hold every Pimcore Data Object.<\/p>\n Second, Pimcore writes the PHP model class. It generates No coding is required for either step. The visual editor writes both the schema and the model for you.<\/p>\n Now build an instance of the class. Open the Data Objects area of Studio to reach the Data Object Tree.<\/p>\n Create the object in three steps:<\/p>\n Pimcore opens the object in the object editor. It shows exactly the fields your class defined, and nothing else.<\/p>\n Fill in the fields for a real product. Enter the name, sku, price, description, upload an image, and tick active.<\/p>\n Every value you type lands in one Pimcore Data Object. The editor mirrors your class layout one-to-one.<\/p>\n A new object starts as a draft. It stays unpublished until you act on it.<\/p>\n The object editor gives you two actions here: Publish<\/strong> and Unpublish<\/strong>. Click Publish<\/strong> to make the record live.<\/p>\n An unpublished object still exists in the tree. Pimcore does not serve it to Data Hub, APIs, or the frontend until you publish it.<\/p>\n Your first Pimcore Data Object is now live. Downstream systems and APIs can read it from this point on.<\/p>\n Need to pull it back? Use Unpublish<\/strong> to return the object to a draft state without deleting it.<\/p>\n Saving the class created several MySQL tables. You rarely touch them, but the map helps when you debug.<\/p>\n Pimcore uses four table types per class:<\/p>\n One modern detail matters. Pimcore 12 and later dropped the old On the PHP side, Studio is the fastest route, but Pimcore also supports code-first workflows<\/a>. Developers can define a class in PHP.<\/p>\n Call The first command regenerates the PHP model classes. The second syncs the database columns to match the definition.<\/p>\n You can also ship a class as JSON. Use Data Model Definitions > Bulk Import<\/strong> to load one, and Bulk Export<\/strong> to dump it.<\/p>\n Heed one gotcha with Bulk Import. It reassigns class IDs on import, so never hardcode a numeric class ID.<\/p>\n Resolve classes by name instead. That keeps every Pimcore Data Object mapping stable across environments.<\/p>\n A class is only the start. Each Pimcore Data Object becomes a feed for the systems around your business.<\/p>\n Data objects push into ERP, CRM, and eCommerce storefronts<\/a>. Connectors carry that structured data to each destination.<\/p>\n Pimcore Data Hub exposes the same objects over GraphQL. Your storefront or app can query them directly, field by field.<\/p>\n You now know the full path in the latest Pimcore. You opened Studio, defined a class, added fields, and published a Pimcore Data Object.<\/p>\n The takeaway is simple. Pimcore Studio turns data modeling into clicks, and it builds the schema and PHP model for you.<\/p>\n Ready to connect your catalog to a storefront or ERP? Talk to the Webkul Pimcore team<\/a> about a connector that moves every Pimcore Data Object where it needs to go.<\/p>\n","protected":false},"excerpt":{"rendered":"Prerequisites<\/h2>\n
\n
Step 1: Open the class editor in Pimcore Studio<\/h2>\n
\n
![\"pimcore-data-object-studio-classes-menu\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-studio-classes-menu-1.webp\")
<\/figure>\nStep 2: Create the class definition<\/h2>\n
![\"pimcore-data-object-create-class-dialog\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-create-class-dialog.webp\")
<\/figure>\n\n
Product<\/code>.<\/li>\nProduct<\/code>. Confirm the dialog to open the full class editor.<\/p>\nStep 3: Add fields with Layout + Data Components<\/h2>\n
General settings for the class<\/h3>\n
![\"pimcore-data-object-general-settings\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-general-settings.webp\")
<\/figure>\nProduct<\/code> class, leave every General field at its default. You can revisit this tab any time.<\/p>\nAdd Layout Component<\/h3>\n
Add Data Component<\/h3>\n
![\"pimcore-data-object-class-editor-fields\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-class-editor-fields.webp\")
<\/figure>\nname<\/code>.<\/p>\nProduct<\/code> class with these data fields:<\/p>\n\n
Product<\/code> structure, ready to save.<\/p>\nStep 4: Save (Pimcore builds the schema for you)<\/h2>\n
Pimcore\\Model\\DataObject\\Product<\/code> so your code can use the type immediately.<\/p>\nStep 5: Create a Pimcore Data Object<\/h2>\n
![\"pimcore-data-object-new-object-tree\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-new-object-tree.webp\")
<\/figure>\n\n
Step 6: Publish<\/h2>\n
![\"pimcore-data-object-editor-publish\"](\"https:\/\/cdnblog.webkul.com\/blog\/wp-content\/uploads\/2022\/11\/pimcore-data-object-editor-publish-1.webp\")
<\/figure>\nWhat Pimcore built under the hood<\/h2>\n
\n
object_<id><\/code> \u2014 the base row for each object.<\/li>\nobject_store_<id><\/code> \u2014 the stored field values.<\/li>\nobject_query_<id><\/code> \u2014 values optimized for grid and listing queries.<\/li>\nobject_relations_<id><\/code> \u2014 the relation links between objects.<\/li>\n<\/ol>\no_<\/code> column prefix, so you never see o_id<\/code> or o_key<\/code> now.<\/p>\nPimcore\\Model\\DataObject\\Product<\/code> is a fully typed model. Your services and controllers load, edit, and save each Pimcore Data Object through it.<\/p>\nPrefer code? Define a Pimcore Data Object class in PHP<\/h2>\n
DataObject\\ClassDefinition::create([...])<\/code> to define the class. Then run two console commands to sync everything:<\/p>\nbin\/console pimcore:build:classes\nbin\/console pimcore:deployment:classes-rebuild --force<\/pre>\n
Where Pimcore Data Objects go next<\/h2>\n
Conclusion<\/h2>\n