Fluent Commerce Logo
Docs
Help & Feedback
Sign In

Cloud Technology Environments

Essential knowledge

Author:

Fluent Commerce staff

Changed on:

5 Mar 2024

Overview

Cloud Technology Environments on the Fluent platform include Sandbox and Production settings. The Sandbox is for testing and training, mirroring the live Production environment. Retailers ensure secure operations using HTTPS and tailored firewall or proxy configurations. These environments are fundamental for smooth retail activities on the Fluent Commerce Cloud platform.

Key points

  • Consistent Naming: Adherence to the Fluent platform's naming convention ensures seamless access and management of different environments.
  • HTTPS Protocol: Utilizing HTTPS is mandatory for secure communication and data protection within Fluent Commerce Cloud.
  • Firewall and Proxy Setup: Proper configuration is essential to enable access while maintaining security against unauthorized entry.
  • Distinct Environments: Understanding the purpose and proper use of Sandbox and Production environments is crucial for testing, training, and live operations.

Naming Convention

All components of the Fluent platform follow a consistent naming convention.

https://ACCOUNT.APP.fluentretail.com

  • ACCOUNT: The retailer’s Fluent Commerce account code which is provided in the Fluent Commerce on-boarding email.
  • APP: The Fluent Commerce application being accessed.

Security

Fluent Commerce advises retailers to only use HTTPS (HTTP over TLS/SSL) to access the Fluent Commerce Cloud platform. By using HTTPS, all communications between the browser and the applications are encrypted.

Firewall and Proxy configuration

Retailers using firewalls or proxy servers need to allow access to *.fluentretail.com and *.parcelpoint.com.au

Note: IP address based restrictions do not work as the Fluent Commerce Cloud platform uses Content Delivery Network (CDN) and dynamic scaling.

Environment Types

A retailer can access Sandbox and Production environments based on their roles and permissions.

Sandbox
  • A stable customer facing environment that has the same version as a production environment.
  • The sandbox environment on the Fluent Commerce cloud platform is used by retailers to perform tests and conduct trainings.
  • The sandbox environment follows a similar naming convention as production, but with sandbox in the domain. An example of sandbox URL’s is:
    • API: https://ACCOUNT.sandbox.api.fluentretail.com
    • ServicePoint: https://ACCOUNT.sandbox.servicepoint.fluentretail.com
    • Fluent Console: https://ACCOUNT.sandbox.console.fluentretail.com
    • Fluent Apps: https://ACCOUNT.sandbox.apps.fluentcommerce.com
Production

It is a stable customer-facing, live environment used by retailers.

Example of production URLs is:

  • API: https://ACCOUNT.api.fluentretail.com
  • ServicePoint: https://ACCOUNT.servicepoint.fluentretail.com
  • Fluent Console: https://ACCOUNT.console.fluentretail.com
  • Fluent Apps: https://ACCOUNT.apps.fluentcommerce.com

Related content

Environment Setup
Edited 253 days ago
Dev Environment Setup for working with the Connect SDK
Edited 218 days ago
Setup your Development Environment for Rules SDK
Edited 2 days ago
Cloud Technology - Architecture
Edited 120 days ago

The Fluent platform leverages advanced cloud technologies to provide a seamless, scalable, cost-effective solution. Designed natively for the cloud, it offers users:

  • Automatic scaling to efficiently manage fluctuating demand without manual intervention.
  • Cost savings through optimized resource utilization and infrastructure sharing.
  • Continuous operations with updates and upgrades that do not disrupt retailer activities.
Webhooks Frequently Asked Questions
Edited 120 days ago

Fluent Commerce doesn't support static IP whitelisting due to AWS Cloud's dynamic nature. Instead, robust authentication measures are in place for webhook security, including cryptographic signing and signature verification. While static IPs aren't recommended, securing webhook endpoints is achievable by configuring unique URLs and firewall rules. Additionally, setting up custom authorizers or message queue validation enhances security. Each webhook establishes a single connection, with inbound and outbound calls dependent on workflow events. For detailed guidance, refer to Fluent's 'Webhook overview' documentation.

Webhook Overview
Edited 145 days ago

Fluent Commerce can post standard webhooks to a configured endpoint so that the third-party system can be notified or react to the provided event. For example, common webhook scenarios include order status updates and shipping notifications.

Fluent Commerce staff

Fluent Commerce staff

Building Blocks
All Building Blocks
Packages & Modules
UI Components
Workflows
Settings
Interface Contracts
Rules
By Type
All Types
How-to Guides
Topics
Essential Knowledge
Releases
Sitemap
Use Cases
Glossary
Legal Resources
Platform Limits
Support Policy
Service Level Agreement (SLA) - Enterprise
Service Level Agreement (SLA) - Professional
Deprecation Policy
Extend Knowledge Content – Terms and Conditions
Information Security Policy
Data Privacy Addendum
System and Organization Controls (SOC) 3 Report

Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.

Fluent Logo