Introduction

This document aims to describe what data a Client (new or otherwise) will be expected to manage in Aurora when launching a new Store.

Responsibilities

Broadly speaking there will be some things that you (the Client) must manage and others that you may or may not outsource to 3rd parties, such as your Agency or even other data integration providers.

Regardless of this, you ultimately remain responsible for all data on your Store, as Aurora Commerce does not provide any data management services beyond UI and support concerns.

That being so, you will need to ensure that you (or your 3rd party representatives) provide data for all of the things required to develop and launch a new Store, the nature of which we go on to discuss below.

Typical New Build Data Requirements

As a minimum, your Agency will need product data to start creating your front-end. This should include the following:

• Product data (we would suggest at least 100 products), with all of the following, fully configured:
  • Images
  • Prices
  • Stock levels (dummy or otherwise)
  • Categories
  • Variations (if you intend to use them)
  • All additional fields, such as Make, Model, Brand, Colour, etc.
    It’s very important that you plan out how your products will be listed in your store in advance of getting your Agency started on work. Aurora can support the use of variations and additional fields if you wish, and the Agency will depend upon these things during their own development(s), depending on how you choose to configure them.
  • Payment Processors:
    • You should have accounts set up and fully configured in Aurora for all of the payment providers that you want to use. Aurora supports all sorts of providers, but each one has its own specific patterns to deploy in the Front-end Templates, patterns that your Agency will need to consider.
    • Locales
    • Languages (not necessarily with complete translations)
    • Currencies
    • Coupons
    • Promotions
    • Blog posts
    • Shipping options
    • Custom content pages, such as Delivery and Returns Information or T's & C's

🚧

All data provided should be as close to the final ‘format’ as possible to ensure that there are no unexpected problems when you eventually switch to having your complete data-set in place. e.g. if you are configuring variations on your products, ensure that you do so in the way you intend to once live.

Other/On-going Data Requirements

Some things are not necessarily required before your Agency can get started with their site build, but are still needed generally speaking, and will require you to manage them. These include, but are not limited to:

• Customers (if you need to import them from another existing Store)
• Redirects
• All feed details (e.g. Feefo Reviews, MetaPack Shipping, etc.)

Typical Data Tools in Aurora

There is a wide range of import and export services available in Aurora that you may wish to be aware of. The use of all of these is entirely at your own discretion and any combination of manual CSV import and API management can be adopted based on what best suits your needs. As such, Aurora does not offer any management of the processes you deploy to use these, however, we will gladly answer any questions that you have surrounding their use while you are working out what workflow you will deploy.

Some important services that may help you get your build started include:

• Product CSV Imports and Exports - For product data
• Aurora API Guide - For any automated data import requirements (using XML)
• Bulk Image Importer (FTP upload) - For product image importing