Once we have the platform set up, it needs basic configuration to start any cash and carry transaction these not just include the Mater Data setup but also the configuration like order number sequence and associate app configurations. In this section, we will cover the basic configuration that is required to set up the platform for trade.
Associate App configuration
Associate App requires seven key configuration sections to enable core and optional functionalities:
Capabilities
Enable optional features to enhance in-store workflows:
add_products_from_listing: Allow adding products from the product listing page.send_email_receipt_from_order_history: Allow sending email receipts from order history.
Commerce components
Configure critical commerce-related settings:
barcode_types: Define barcode types for scanning operations. Refer to Configuring commerce components in NewStore Associate App for detailed steps.
Return process configuration
Set up return-related options such as policies and workflow behavior. This will be covered in detail in Module 2: Returns & exchanges.
UI configurations
Manage visual and user-interface related preferences:
Tax exemption settings
Associate App logo (this should be in Base64 format, refer attached sample for more details.)
Customizations
Adjust the app behavior and layout via custom scripts or UI changes. Refer to Configuring customizations in NewStore Associate App for examples and use cases.
Release toggles
Control access to new or optional features:
Enable runner
Enable quantity picker
External integration
Configure loyalty program integration and authentication endpoints.
API reference
Use the Update Associate App Configuration API to apply these settings.
Refer sample associate app configuration attached for reference.
Checkout configuration
Establish and control checkout behavior across the platform and in Associate App.
API reference
Refer Configuring checkout operations for tutorial to understand the checkout configuration.
Payment configuration
To process in-store payments, configure accepted payment methods. This exercise includes:
cash
non_integrated (example, external payment terminals)
Tutorial
Refer to Configuring payment options for setup steps.
Refund options will be addressed in Module 2: Returns & exchanges
Order ID sequence
When an order is created, this configuration will determine the pattern in which the order number will be generated.
API reference
Use the Set order ID sequence parameters API to configure the order number format.
If the sequence is not set, a default using UUID v7 will be assigned. Orders will stop using this default ID once the sequence is configured.
Financial document configuration
Configure the tenant address for the retailer and the Invoice id patternso that the address will be used in different places including Invoice generation.
API reference
Use the Create financial documents configuration API to define invoice number and address formatting.
Taxes
NewStore platform offers a convenient tax calculation feature that can automatically determine taxes for merchandise and shipping. This feature supports four different modes, providing flexibility for various business needs. Configuration options are available at both the global and store levels, allowing for tailored settings. Additionally, the platform supports integrations with Avalara, Vertex Cloud, and custom integrations, as well as a flat rate option. The fixed rate can be configured at multiple levels.
Globally at the Tenant level
Per country level
Most granular which is the store level.
Important
This exercise only covers the flat rate configuration.
Refer to Configuring Avalara for tax calculation to configure Avalara for tax calculation and Avalara tax exemption class mapping. Tax committing using the productized Avalara integration is limited to in-store orders, where taxes are calculated within the NewStore platform. For more details, see Tax committing use cases.
Refer to Configuring Vertex for tax calculation to configure Vertex for tax calculation.
If the retailer chooses to bring their own tax engine, then refer Setting up a custom tax provider to understand how to configure a custom tax solution.
It’s always a best practice to configure offline tax rates to make sure if the integration to the tax engine fail, the default tax rate is used to calculate taxes. Refer Fixed Rate fall back option configuration to enable the config.
Tenant-level tax config is mandatory; configure this first, before proceeding with store-level tax setup.
Configure at the global level if the settings are uniform across all stores, and at the store level if the settings are unique to each store.
Use the Taxes configuration API to configure the fixed tax rate.
Sample payload
The following examples set the fixed tax rate at 0.05% with a tax name as FIXED RATE.
{
"fixed_rate": {
"tax_name": "FIXED RATE",
"tax_rate": 0.05
},
"tax_calculation_strategy": "fixedrate"
}