Data export to S3 - database structure reference

When requesting a data export to S3, you need to specify which database tables to include.

If you know exactly which tables contain the data you need, you can request an export for just those specific tables. However, if you’re unsure where certain data lives or need a complete picture of a business domain, this guide helps you identify all the relevant tables.

How Spryker stores data

Spryker stores business data across multiple relational tables that together form logical domain aggregates. For example, an order is not stored in a single table but spread across tables for addresses, items, payments, shipments, and more.

This guide organizes tables by business domain to help you:

• Discover which tables are related to a specific domain.
• Ensure you don’t miss important data when exporting a complete domain.
• Identify project-specific tables that extend standard Spryker tables.

The tables are grouped into two categories:

• Standard tables: The default Spryker tables for each domain, listed in Standard tables by domain.
• Project-specific tables: Custom tables your project may have added. See Identify project-specific tables.

Standard tables by domain

The following sections list the standard Spryker tables for common business domains. You can reference these lists or use them as a baseline when requesting an export.

Order

Tables containing order data, including items, addresses, payments, shipments, returns, and reclamations.

Order Management System (OMS)

Tables containing order state machine data, including states, transitions, timeouts, and reservations.

Product

Tables containing product data, including abstract and concrete products, attributes, images, labels, options, bundles, and relations.

Customer

Tables containing customer data, including addresses, groups, notes, and company associations.

Merchant

Tables containing merchant data, including profiles, commissions, opening hours, and product associations.

Price

Tables containing pricing data, including product prices, scheduled prices, and merchant-specific pricing.

Stock

Tables containing inventory and availability data.

Category

Tables containing category hierarchy, attributes, and images.

Identify project-specific tables

Your project may include custom tables that extend the standard Spryker domains. To ensure complete exports, identify these tables and include them alongside the standard tables.

Run the following SQL query against your database to find tables related to a specific domain. Replace the table names in the IN clause with the base tables of your target domain.

Example for Order domain:

(
    -- Tables that reference order tables
    SELECT DISTINCT kcu.TABLE_NAME AS table_name
    FROM information_schema.KEY_COLUMN_USAGE kcu
    WHERE kcu.REFERENCED_TABLE_SCHEMA = DATABASE()
      AND kcu.REFERENCED_TABLE_NAME IN ('spy_sales_order', 'spy_sales_order_item')
)
UNION
(
    -- Tables referenced by order tables
    SELECT DISTINCT kcu.REFERENCED_TABLE_NAME AS table_name
    FROM information_schema.KEY_COLUMN_USAGE kcu
    WHERE kcu.TABLE_SCHEMA = DATABASE()
      AND kcu.TABLE_NAME IN ('spy_sales_order', 'spy_sales_order_item')
      AND kcu.REFERENCED_TABLE_NAME IS NOT NULL
)
ORDER BY table_name;

Compare the query results with the standard tables list. Any tables not in the standard list are project-specific and should be included in your export request.

This query also detects optional Spryker features that may be installed in your project but not listed in the standard tables, such as ECO module tables.

Next steps

Once you have identified all required tables for your domain, request an export setup by submitting a support ticket with your table list.