Terug naar de documentatie
Zoekvoorstellen
""
0
Results
Alles bekijken van
“3D”
Recent searches
Clear all
Search not found
Search anyway
0 Results
Clear search
Everthing you need to know become a oneCORE user.
The metadata on oneCORE is used differently depending on where it is. Metadata on Pages, Products, Blogs, Categories is mainly used for [SEO tags](https://colengo.com/en/blogs/standard-key-tags-for-seo-and-social-media). Metadata on Editions acts as an identifier for retrieving external prices. Metadata (JSON) on Account page is used to fetch data from external tools or systems.
They may sound similar, but they serve different purposes. A shipping class indicates the product or edition’s processing time and cost required before it is ready to ship. A shipping method refers to the logistics options available to customers at checkout, allowing them to choose the one that best suits their needs.
If you’re working with multiple projects in oneCORE, you’ll often come across the terms “Organization” and “Company,” and they don’t mean the same thing. An Organization represents the entire environment — it includes all projects that exist within the same database. A Company refers to each individual project inside that organization. For example, when something is described as being “at the company level,” it means the data applies only to that specific project and does not carry over to other projects within the same organization.
Please provide your username or oneCORE ID to together@colengo.com
oneCORE is designed for configurable products, where different parts of a product can be customized. Product editions represent each variation of a product — for example, size, color, or material. Master editions serve as a higher-level grouping that multiple product editions can be linked to. This allows editions to share the same stock and settings, making management and setup much simpler.
Product configuration rules help control how different product editions can be combined. These rules define conditions to prevent invalid or unsupported configurations. For example, you can create a rule that blocks certain materials from being paired with specific colors if that combination cannot be produced.
“Categories” help users organize products into groups and are primarily intended for displaying product structure on the live website. A product can belong to multiple categories. “Catalogs” are used for backend setup and management. They group products for configuration purposes, and products within the same catalog can share settings such as editions, configuration rules, and more. Unlike categories, a product can belong to only one catalog.
Enthousiast? Doe de quickscan
Zie direct of jouw maakbedrijf en ons platform een perfecte match zijn.