> ## Documentation Index > Fetch the complete documentation index at: https://docs.remark.ai/llms.txt > Use this file to discover all available pages before exploring further. # NewStore > Connect NewStore so agents can look up orders, search order history, find nearby stores, and check store stock. Remark's NewStore integration lets agents read orders and store stock from your NewStore tenant during shopper conversations. It can also sync your NewStore stores into Remark, so agents can help shoppers find a store near them. ## What the integration does Once connected, Remark can: * Look up an order and report its status, shipments, delivery dates, and tracking links * List a customer's recent orders, in store and online * Sync your NewStore stores as Remark store locations * Check how many units of a variant a store has on hand Every NewStore action reads data. NewStore remains the system of record for orders, fulfillment, and inventory. ## Before you start You need: * The **Integrations & products** permission. For details, read [Team member permissions](/dashboard/team-member-permissions.md). * Your NewStore domain * A NewStore API client ID and client secret Your NewStore domain should look like: ```txt theme={null} my-tenant.p.newstore.net ``` Remark reads locations, stores, orders, and store stock with the client credentials, so the client needs access to those NewStore APIs. ## Connect NewStore 1. Open **Settings > Integrations** in the Remark dashboard. 2. Under **Other integrations**, find **NewStore** and select **Connect**. 3. Enter your **Domain**, **Client ID**, and **Client secret**. 4. Select **Connect**. Remark requests a token and reads your NewStore locations to test the credentials. If the test fails, the integration is not installed. ## Sync store locations Store location sync starts off. To turn it on: 1. On the connected NewStore integration, turn on **Sync store locations**. 2. Select **Save**. Remark syncs when you turn on the setting and save, and again if the domain changes while the setting is on. Store locations don't sync on a schedule. After you open, close, or move a store in NewStore, select **Sync now** next to **Sync store locations**. The button works once the setting is on and saved, and Remark shows **Store location sync queued** when the sync starts. Each sync: * Imports each NewStore location of type store, with its name, address, phone number, time zone, and coordinates. The NewStore location ID becomes the store code. * Marks stores disabled in NewStore as inactive * Deletes store locations that NewStore no longer reports * Leaves your store locations unchanged when NewStore reports no stores Synced stores appear with the store locations you manage through the [Store Location API](/guides/product-import.md#store-location-api). ## Add NewStore actions to an intent Connecting NewStore makes its order actions available to your workspace. After the first store location sync, **Check NewStore stock** becomes available too. Active store locations with coordinates also enable Remark's **Find nearby stores** action. To let the agent use these actions in conversations, add them to a relevant [intent](/dashboard/intents.md), such as an order status or store availability playbook. | Action | What it does | Required inputs | | - | - | - | | **Look up a NewStore order** | Reads one order's status, items, shipments, delivery dates, and package tracking links. The agent reports split shipments separately. | Order number, plus the customer's last name or the email address on the order | | **Search NewStore order history** | Lists up to 20 of the customer's most recent orders, in store and online, with each order's number, status, exceptions, where it was placed, and where it's fulfilled from. The agent can narrow the list by status, such as `on_hold`, or by exception, such as `insufficient_stock`. | Email address and last name | | **Check NewStore stock** | Reads how many units of one variant a store can sell right now | Store code from **Find nearby stores**, and the variant's SKU | | **Find nearby stores** | Finds active store locations near a ZIP code, city, or address, sorted by distance. Returns five stores unless the agent asks for a different number. | A location | Reference the actions in the intent instructions where the agent should use them: ```txt theme={null} Ask for the order number and the shopper's last name or email, then use @NewStore.GET_ORDER. If the shopper has no order number, collect their email and last name and use @NewStore.GET_CUSTOMER_ORDERS. To check a store, use @Remark.FIND_STORES with the shopper's ZIP code, then @NewStore.GET_STORE_STOCK. ``` Test the intent in the [Playground](/dashboard/playground.md) before enabling it for live conversations. ## Customer verification The order actions check the shopper's details against NewStore before returning order data. * **Look up a NewStore order** needs a last name that matches the shipping address, the billing address, or the customer name on the order, or an email that matches the billing email or the customer's email. When neither matches, the agent reports that no order matches the details, without saying whether the order number exists. * **Search NewStore order history** returns only orders whose customer email matches and whose customer name ends with the given last name. ## Store stock **Check NewStore stock** finds the variant in your Remark catalog by SKU and asks NewStore for stock under the variant's UPC. If the variant has no UPC, Remark uses the SKU as the barcode. The count reflects what the store has on hand, which can differ from online availability. When NewStore has no stock record for the variant at that store, the agent tells the shopper it couldn't confirm stock rather than reporting zero. ## Playground behavior NewStore actions read live data in the Playground. To test order lookups, use a real order number with a matching last name or email. Stock checks return current counts from your NewStore stores. ## Troubleshooting ### Domain validation fails Confirm that the domain ends in `.p.newstore.net`, such as `my-tenant.p.newstore.net`. The first part of the domain identifies your NewStore tenant. ### Credentials are rejected If the error says the NewStore token request returned a status code, confirm the client ID and client secret, and confirm they belong to the tenant in the domain. If the error says NewStore answered `GET /v0/locations` with a status code, the client authenticated but can't read locations. Ask your NewStore administrator to grant that access. To change credentials later, open **More options** on the NewStore integration, select **Manage connection**, and enter the new values. ### Sync now is unavailable The button works only after **Sync store locations** is on and saved. Turn on the setting, select **Save**, then select **Sync now**. ### Find nearby stores doesn't return a store Confirm that the store is enabled in NewStore and has latitude and longitude on its address. Then select **Sync now**. ### An order can't be found Confirm the order number as printed on the confirmation, and confirm that the last name or email matches the order in NewStore. For orders without a number, use **Search NewStore order history** with the shopper's email and last name. ### Stock is reported as unknown Confirm that the SKU matches exactly one variant in your Remark catalog and that the variant's UPC matches the barcode NewStore uses. If several variants share the SKU with different UPCs, the stock check fails until the SKUs are unique. > [!NOTE] > > Need help connecting NewStore or testing its actions? Contact `support@remark.ai`. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.