> ## Documentation Index > Fetch the complete documentation index at: https://www.twicecommerce.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # What changes from TWICE 1.0 > How TWICE 2.0 reshapes your 1.0 catalog, stock and prices, what you set up again, and what stays in 1.0. Read this before you start the [migration path](https://www.twicecommerce.com/docs/guides/migration/overview). TWICE 2.0 has its own data model, so your 1.0 setup is rebuilt in 2.0's shape rather than copied. Each table names a 1.0 object, what replaces it, and what to do about it. ## Your catalog and stock Plan your catalog in three layers: what you sell, what you own, and the rule that connects them. A 1.0 product carried all three. | In 1.0 | In 2.0 | What to do | | - | - | - | | A store | A [location](https://www.twicecommerce.com/docs/concepts/admin/locations.md), with its own opening hours, pickup and return methods, and sales channels | Recreate each store as a location. Merge stores you split only to work around 1.0, such as one shop run as three stores. | | A product | A [listing](https://www.twicecommerce.com/docs/concepts/catalog/listings.md): what the customer buys, at what price, with what content | Create one listing per product you still sell. | | An article | A [stock item](https://www.twicecommerce.com/docs/concepts/inventory/stock-items.md), grouped under a [SKU](https://www.twicecommerce.com/docs/concepts/inventory/skus.md) | Keep each SKU code as it was in 1.0, so printed labels and barcodes keep working. | | A single article, or a bulk article | A stock item [tracked individually, or by quantity](https://www.twicecommerce.com/docs/concepts/inventory/inventory-tracking.md) | Keep the same choice per SKU. | | The articles a product draws on | [Inventory rules](https://www.twicecommerce.com/docs/guides/catalog/listing-inventory-rules.md) on the listing, matching stock items by SKU, name or attribute | Give every listing with stock behind it a rule. A listing with no rule has unlimited availability. | | A package | A listing with one rule per component | Give each component its own rule. Components placed in one rule make the package available when any one of them is in stock. | | Variants, such as sizes | [Options](https://www.twicecommerce.com/docs/concepts/catalog/variants.md) on the listing, each drawing only its own stock | Check that each option draws its own units and no others. | | A category | A [collection](https://www.twicecommerce.com/docs/concepts/catalog/collections.md) | Recreate the categories customers browse by. | | Custom inventory fields | [Attributes](https://www.twicecommerce.com/docs/concepts/admin/attributes.md) on stock items | Recreate the fields you still use. | | A product limited to some sales channels, or hidden from the online store | The listing's **Sales channels**, on its **Publishing** tab | Copy every channel restriction across. | | A duplicate product, made to sell the same items two ways | One listing | Migrate the original. Leave the copy behind. | | Maintenance time between rentals | A [buffer time](https://www.twicecommerce.com/docs/guides/inventory/set-a-buffer-time.md) on the SKU | Carry the same minutes across. | ## Your prices Settle these with whoever moves your data, before the first price is written. | In 1.0 | In 2.0 | What to do | | - | - | - | | A fixed price per duration (4 hours, 1 day, 1 week) | Fixed rows on the listing's [price table](https://www.twicecommerce.com/docs/concepts/catalog/price-tables.md), or one [rate-based](https://www.twicecommerce.com/docs/concepts/catalog/rate-based-pricing.md) row that scales with the duration | Keep fixed rows to keep every tier price exactly. Choose rate-based for a simpler table, and accept that tier prices become approximations. | | A day counted within opening hours | A day row that ends at closing time | Keep the closing-time behaviour on these rows. | | Prices entered with or without tax | **Tax calculation** under **Settings → Taxes** | Read it from a real 1.0 order, before any price comes in. | | A free accessory offered with a product | An [add-on listing](https://www.twicecommerce.com/docs/guides/catalog/create-an-addon-listing.md) attached to the listings it goes with | Make free accessories add-ons, unless everything you offer is free. | | Insurance or a damage waiver | A cart add-on, offered once per cart | Recreate it as a cart add-on in your online store's settings. | ## What your customers read Plan to write these yourself. 2.0 starts each one from its own default text. | In 1.0 | In 2.0 | What to do | | - | - | - | | Product descriptions with Markdown formatting | Rich text in the listing editor | Check no listing shows raw `**`, `***` or `[text](link)` on the storefront. | | Terms and policies | Policies under **Settings → Terms & Policies**, linked from the storefront footer and the checkout | Write your own terms, privacy and cookie policies. | | Order emails | Email templates under **Settings → Emails**, kept separately per language | Edit every language you sell in. A change in one language leaves the others on the default text. | | Receipts and agreements | Document templates under **Settings → Documents** | Check each one renders your business and order details. | | Text in more than one language | The translation editor under **Settings → Translations & Languages**, with coverage per language | Bring every language you sell in to full coverage. | ## What you set up again Expect to redo each of these in 2.0, whichever way your data moves. | In 1.0 | In 2.0 | What to do | | - | - | - | | Your payment connection | Stripe, connected through TWICE | [Connect payments](https://www.twicecommerce.com/docs/guides/migration/connect-payments.md). | | Staff logins | Users, each with a role and the locations they work at | [Invite everyone again](https://www.twicecommerce.com/docs/guides/migration/set-up-and-train-your-team.md). | | API access and integrations | The [Admin API](https://www.twicecommerce.com/docs/concepts/integrations/overview.md), with new [API keys](https://www.twicecommerce.com/docs/concepts/integrations/api-keys.md) | Repoint every integration at the new API. | | Your store's web addresses | A TWICE subdomain, or your own domain | Update every link you control. 1.0 addresses do not redirect. | | Your subscription | A plan tier, priced per location | [Move your subscription](https://www.twicecommerce.com/docs/guides/migration/move-your-subscription.md). | ## What stays in 1.0 Keep these in 1.0 and finish them there, whichever way your data moves. The [last step](https://www.twicecommerce.com/docs/guides/migration/run-both-systems-down.md) covers each one. | Stays in 1.0 | What to do | | - | - | | Orders and bookings made before the switch, including ones dated after it | Fulfil them in 1.0. | | Stock out with a customer on a 1.0 order | Take it back in 1.0, and block it in 2.0 with a [reservation](https://www.twicecommerce.com/docs/guides/inventory/reserve-a-stock-item.md). | | Deposits you hold | Release or charge them from the 1.0 order. | | Saved cards | Ask customers to pay again in 2.0. | | Order history, invoices and finance reports | Export them before 1.0 access ends. | ## Related articles > [card] [Bring your data across](https://www.twicecommerce.com/docs/guides/migration/bring-your-data-across) > > The three ways your 1.0 data reaches 2.0. > [card] [Migrating from TWICE 1.0](https://www.twicecommerce.com/docs/guides/migration/overview) > > The ten steps, in order. > [card] [Listings](https://www.twicecommerce.com/docs/concepts/catalog/listings.md) > > What a listing is, and what it holds. > [card] [Stock item vs SKU](https://www.twicecommerce.com/docs/inventory/stock-item-vs-sku.md) > > What TWICE counts as a unit, and what groups those units. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.