Standard Aurora Rollout Task Allocation

📘

PLEASE NOTE: We will move forward to a Stage only once the previous Stage is fully signed off.

PRE ROLLOUT

• Aurora Commerce engage with you to establish the required Site set up. We then settle the Scope with you = Unknown, but expectation of approximately 5 DAYS BILLABLE

STAGE 1

• We set up the necessary Aurora platform test site, ensuring overall access is granted (ftp / http / https) for you to work on Aurora  = 5 DAYS BILLABLE
• You Scope the full project (Aurora Commerce brought in as required) = Unknown, but expectation of approximately 3 DAYS BILLABLE
• Aurora Commerce Bespoke work required is issued by you to us, and this is Scoped by us = Unknown, but expectation of approximately 5 DAYS BILLABLE
• Bespoke work required from us is Specced by us = Unknown, but expectation of approximately 3 DAYS BILLABLE
• We issue the Specification for Sign Off by you (with Sign Off sheet).
• We implement required edits towards Sign Off; three rounds are possible = Unknown, but expectation of approximately 3 DAYS BILLABLE

📘

Aurora Test site created: Server costs are incurred at this point, and this should only be set up when your Agency is ready to actually start work.

📘

Micro Services set up: This should be done only when your Agency is ready to work on payments, due to costs. Your Agency is to please issue a time-frame on this. The Micro Services set up is not specifically noted below, but will be considered alongside the 'Aurora Commerce supports your Agencies Build (Aurora Commerce brought in as required).' section below under STAGE 2.

STAGE 2

• Aurora Commerce Planning and Go Live documentation is compiled = Unknown, but expectation of approximately 3 DAYS BILLABLE
• We support your Agencies Build (Aurora Commerce brought in as required) = 5 DAYS BILLABLE

STAGE 3

• We complete all outstanding Aurora Commerce required and Specced works = Unknown, but expectation of approximately 10 DAYS BILLABLE

  • We QA (Quality Assurance) our works and implement any fixes = 3.5 DAYS BILLABLE
  • We release our works for Sign Off (with Sign Off sheet).
  • We implement required edits / fixes towards Sign Off; three rounds are possible = Unknown, but expectation of approximately 3 DAYS BILLABLE

STAGE 4

• The Sign Off is obtained and a Go Live date is able to be settled by Aurora Commerce with all parties.
• We prepare the Go Live and the final QA Pre-live Checklist check is completed prior to the Go Live date being confirmed = 3 DAYS BILLABLE
• Go Live is completed = 2 DAYS BILLABLE

STAGE 5

• Post Go Live the first two weeks are fully ad-hoc supported by Aurora Commerce = 5 DAYS BILLABLE

Detail of During Build/Rollout Task Allocation:

Please find below the standard Aurora Commerce rollout requirements in detail; your assigned Account Manager can discuss and / or give you further information on this process as required.

• International deployment, excluding integrations:

  • Either add a new currency / language onto your main site: achievable within 1 working days

  • If you wanted a new domain setup: achievable within 5 working days

  • What we need to train your Agency up in. Please note, the separation between Aurora Commerce and you is currently that you are unable to manipulate any real-time data. 

  • Your Agency is expected to implement all of the front-end templates

    • CSS

    • HTML

    • Javascript

    • Your Agency is expected to use Smarty 3 for the front-end implementation. Smarty 3 offers a wide range of features that will allow data to be manipulated within the templates. 

    • Aurora APIs:

      • Documentation: Aurora API Guide

      • Examples of existing APIs that your Agency would be able to use

        • Extracting all products from Aurora

        • Extracting real-time price updates

        • Extracting real-time stock

        • Updating stock, products and prices in real-time

        • Extracting merchandising rules from Aurora

        • Performing searches against our product database

        • Real world examples:

          • Blacks have iPads in their stores that integrate into Aurora’s APIs to pull all the products, images, prices, stock, merchandising, translations and content into their App-based interface. For this, Aurora is considered to be the 'master' for all data, which is then pulled out into this third party application.
            Orders placed placed via this platform are pushed into Aurora.
          • JD Ireland has a dedicated mobile app + mobile site that whilst not built by Aurora Commerce are all powered via our APIs on another platform.
          • Intelligent Reach call the Aurora APIs to extract all the products. This is then fed into their system so Clients can manage all of their 3rd party channels in one place (e.g. Amazon / eBay and many more).
          • The Agency is limited in what they can achieve on the front-end of Aurora, as the data they manipulate is on the structure offered by Aurora and exposed via back-end / APIs, but cannot define custom data structures or data sources themselves. This is what Aurora Commerce are opening up.

All quotes assume this is for a new Site with:
No existing Aurora DB to be installed / copied, and so all instances provided with base Aurora Demo content (until the bespoke data import).
No independent API server(s).