User Guide
  • Intro
    • Welcome
      • About DotApparel
      • What is DotApparel?
      • Where is it hosted?
      • What platform(s) do we support?
      • How does syncing work?
      • Solution architecture
      • Definition of “Instance”
      • Security Overview
    • Implementation
      • Google Cloud and Firebase
  • Quick Links
  • Core
    • Overview
    • Dashboard
    • Orders
      • Mappings
      • Integrations
    • Returns
      • Mappings
    • Products
      • Mappings
        • Default mapping rules
      • Translations
      • Markets
      • Publishing products
    • Inventory
      • Mappings
        • Examples
          • Ignore Sync
          • Inventory Buffer
          • Keep Items Sold Out
          • Unlimited Inventory
    • Customers
    • Rewards
    • System Alerts
    • Settings
      • Shopify Locations, DotApparel Locations and Inventory Buffers
      • ERP credentials
      • Product images
      • Fulfillments
      • Payment gateways
      • Gift cards
      • Refunds
      • Notifications
      • Harmony Integration with DotApparel
    • Modules
      • Ship From Store
      • Local Pickup/Click & Collect
      • Shopify Markets
      • Returns
        • Australia Post (AusPost)
        • Loop Returns
      • Auto-Refunds
        • Refunding Shopify Orders from POS (In-Store)
      • Integrate with Brauz (app)
      • Integrate with The Wishlist (app)
    • Release Notes
    • Troubleshooting
      • FAQs
      • How to raise a support ticket for an issue
      • Good and bad examples of a problem ticket
      • Want to enable a new omnichannel feature?
      • Want to integrate a marketplace using DotApparel?
  • Customers
    • Overview
      • Email Examples
    • Getting Started
      • Understanding Customer Setup in your ERP
      • Data Sync
      • Configuration
      • Testing
    • Data Export Approaches
      • Option A: Consultant
      • Option B: In-House
    • Apparel21 Export Templates
    • Apparel21 Export Changelog
    • Dashboard
    • Customers
    • Orders
    • Translations
    • Mappings
    • Settings
    • Support
  • Loyalty
    • Overview
    • Getting Started
      • Terminology
    • Data Sync
      • Workflows
    • Front-End Implementation
    • Rewards Redemption
    • Rewards Emails
    • Things To Know
Powered by GitBook
On this page
  • Setup [Merchant]
  • Installation & Configuration [DotApparel]
  • Testing [Both]
  • Launch [DotApparel]
  • Launch [DotApparel]

Was this helpful?

Export as PDF
  1. Intro

Implementation

What's it look like to implement a DotApparel solution?

PreviousSecurity OverviewNextGoogle Cloud and Firebase

Last updated 9 months ago

Was this helpful?

Setup [Merchant]

Create your Google Cloud account and Firebase projects on paid Blaze Plan. Please note to ensure that your project is not downgraded at any point, it is mandatory that billing details are added at the time of Project creation. If you need help, reference our .

Provide Firebase access

  • Firebase Production project

  • Firebase Staging project

  • Invite support@dotdev.com.au an owner.

Provide Apparel21 access

  • Retail API URL and logins

  • Whitelist VPN IP (46.102.153.187)

  • Whitelist Solution Static IP (provided once the Firebase project is created)

Provide platform access

  • Core (Shopify)

    • Provide URLs for us to request collabrator access

    • Approve request and grant store access

    • Store permissions: Create custom app

    • Store permissions: Export products

    • Provide Cloudinary logins if using for images

  • Customers (Klaviyo)

    • Invite support@dotdev.com.au an admin

  • Loyalty (Yotpo)

    • Invite support@dotdev.com.au an admin

Installation & Configuration [DotApparel]

Once the steps above have been completed, we will commence on the the installation and configuration. To kickoff this part of the project we'll have an onboarding call to run through a reference sheet and collection all the information we need.

During this phase we'll setup, configure and deployment your solutions ready for testing.

Testing [Both]

We will conduct various testing scenarios and only proceed once each one has been successfully passed. Subsequently, our Customer Success Manager will provide your team with a Google Sheet containing the required testing scenarios which you will need to complete.

We will both work through this phase until both sides are comfortable your solution has been configured correctly and we are ready for launch.

Once final approvals has been given we'll conduct a launch planning call and discuss how this will play out, specifics around data migration and any down time if required for front-end changes.

Launch [DotApparel]

Upon successful completion of all testing scenarios, we will initiate the necessary steps to deploy your solution into your production environment, as agreed upon for the go-live day and time.

Pre-launch

  • Any required frontend changes deployed

  • Data migrations and syncing processes completed

  • Final checks and testing before go-live

  • Launch your DotApparel solution

Post-launch

For merchants using existing custom solutions, we will keep these running for around one more month to process any remaining data. Afterward, we will arrange to terminate your old solution (this should also stop services since they’re no longer needed at this point).

Launch [DotApparel]

All our support in handled through in-solution widgets and also through our dedicated support@dotapparel.com.au inbox. We have a dedicated team in Australia that monitor throughout each day and aim to adhere to our set SLAs.

During the post-launch hyper-care period we also monitor your solution using the dashboard and help to resolve any configuration issues or things that might arise.

We also have urgent support available after hours by calling 1800DOTANZ.

Google Cloud & Firebase Setup guide