This guide explains how to connect Anchanto OMS to HexaSync so that HexaSync can access your store data on Anchanto OMS. This data is used to assess the quality of your product and inventory data, and to check the data before you connect to another system.
Before you start
- A Beehexa account. If you do not have one yet, sign up on the same page.
- The API Access Token of Anchanto OMS. If you do not have one, contact your Anchanto account manager or Anchanto support to get a token.
- The SMP Code (
ss_code) of the store you want to connect. See how to get it in the section below. This is the code Anchanto uses to identify a connected sales channel. It is not the store code field of the store. - The environment the token was issued for: Production (the live Anchanto OMS) or Staging (Anchanto’s test environment).
Get the SMP Code of your Anchanto store
The SMP Code is the code Anchanto OMS uses to identify each connected store (sales channel). HexaSync needs this code to know which store to read data from.
- Sign in to Anchanto OMS.
- Go to INTEGRATION → Ecommerce Channels.
- Find the store you want to connect to HexaSync in the list.
- Copy the SMP Code of that store. An SMP Code looks like
SS0000012345.
Note: The SMP Code is different from the store code field of the store. Use the value that starts with SS in the INTEGRATION section.
Part 1: Authorize the Anchanto OMS connection on HexaSync
Step 1: Sign in to HexaSync
- Go to HexaSync Automation Engine and sign in with your Beehexa account.
Step 2: Start the Anchanto OMS connection
- Open the Anchanto OMS connection setup page on HexaSync.
- On the Check connection details screen, select Connect.
Step 3: Enter your Anchanto store details
- On the Connect HexaSync to your Anchanto OMS store screen, enter the following details:
| Field | Value to enter |
|---|---|
| API Access Token | The API token Anchanto issued for the OMS account. This field hides the characters as you type. Paste the whole token and do not add spaces. |
| Store Code (ss_code) | The SMP Code of the store (how to get the SMP Code). HexaSync trims spaces at both ends and converts the value to uppercase before sending it. |
| Anchanto Environment | Select Production for the live OMS, or Staging for the test environment. The default is Production. |
- Check all three values again, then confirm.
Note: If you select the wrong environment, the token check fails. A token issued for Production does not work on Staging, and the reverse is also true.
Step 4: HexaSync checks the token
HexaSync shows Checking Your Anchanto Token while it runs the check. HexaSync calls the Anchanto OMS API on the environment you selected to confirm that the token can see the store with the SMP Code you entered. If the token is valid, HexaSync encrypts and stores the credential, and from then on it does not show the token again.
HexaSync calls the Anchanto server that matches the selected environment:
| Environment | Anchanto OMS server |
|---|---|
| Production | api-apac-oms.anchanto.com |
| Staging | api-omsuat.anchanto.com |
The credential is named in the form Anchanto OMS - <SMP Code> (<Environment>), for example Anchanto OMS - SS0000012345 (Production).
If the check fails, HexaSync shows HexaSync Could Not Verify Your Anchanto Token. Select Back to my store details to go back and correct the details, and see how to fix the error in Part 4.
The Anchanto token does not expire, so HexaSync does not need to refresh it periodically.
Step 5: Complete the connection and create the Connector App
After the token is verified, the process continues to the step that creates the Connector App. When the connection is complete, HexaSync shows Connection successful. The suggested name of the Connector App is the store name that Anchanto returns, or the SMP Code if Anchanto does not return a store name.
HexaSync starts pulling data within 30 minutes after the Connector App is created. Check the connection by following Part 3.
Part 2: Re-authorize the Anchanto OMS connection on HexaSync
Do this when Anchanto reissues the token, or when you need to enter the connection details again. Connecting the same store on the same environment again updates the existing credential and does not create a new one, so the Connectors that use that credential are not affected.
Step 1: Open Settings in the Anchanto OMS Connector App
- Open Connector Apps and select the matching Anchanto OMS Connector App. Select Settings in the left menu.
Step 2: Select Re-authorize
- In Settings, find the Anchanto OMS credential and select Re-authorize.
Cannot use Re-authorize? Only the owner (creator) of the Anchanto OMS credential has permission to update it. Contact the owner of the credential.
Step 3: Re-enter the store details
- On the Connect HexaSync to your Anchanto OMS store screen, paste the new token.
- Keep the same SMP Code and environment as in the previous connection. These two values may already be filled in.
- Confirm.
Note: If you enter a different SMP Code or environment, HexaSync creates a new credential for that store or environment instead of updating the old credential.
Step 4: Finish
HexaSync checks the token, updates the credential and takes you back to the Connector settings page. If the check fails, see Part 4.
Part 3: Check that the connection works
The connection is successful when HexaSync takes you back to the Connector App or to the Settings page of the Anchanto OMS Connector without an error message. If you connect when you do not have a Connector App yet, this is when HexaSync shows the Connection successful screen. Confirm it again in two places in HexaSync.
Check the connection details
- Open Connector Apps and select the Anchanto OMS Connector App of the store.
- Go to Settings. The Anchanto OMS connection row shows a credential named in the form
Anchanto OMS - <SMP Code> (<Environment>), in place of the Authorize button. - Check that the SMP Code and environment in the name match the store you want to connect.
Check the data
Run an Anchanto OMS data pull task manually. This is the part that actually calls Anchanto OMS, so it is the most accurate test: the task must finish without an authorization error.
- Select Tasks in the left sidebar, then select an Anchanto OMS data pull task, for example the inventory task.
- Open the Other Actions list and select Pull to run the data pull manually.
- Wait for the run to finish, then open the result. The result has no authorization error and contains records pulled from your store.
Note: If the task reports an authorization error or an access error, the credential is not working yet. Update the token by following Part 2 before you turn on the schedule. The Connector App only reads data from Anchanto OMS. It does not create or update data in Anchanto OMS.
Order of Header, Product and Stock data
- The [Anchanto OMS] Inventory Product Headers task pulls data from Anchanto OMS before the other tasks.
- When the Header task finishes pulling data, HexaSync puts the Header data in a queue to pull the Product and Stock data for each item. The queue is processed in 5-minute cycles, so Product and Stock data may appear gradually after the Header task reports success.
Part 4: Common errors and how to fix them
When the token check fails, HexaSync shows the HexaSync Could Not Verify Your Anchanto Token screen. The first bold line tells you the cause, and the Technical details line at the bottom of the screen gives the error code, the error content and the HTTP code. Write this line down before you try again, because the support team will need it. The Back to my store details button takes you back to the screen where you enter the details.
| Message | How to fix it |
|---|---|
| Store <SMP Code> on <environment> is already connected by another HexaSync user | Another HexaSync user has already connected this store on this environment. Each store on one environment has only one credential. Ask the owner to share the credential with you, or contact your HexaSync administrator. |
| Your HexaSync account is not allowed to register credentials | Your HexaSync account does not have permission to create connections yet. Ask your HexaSync administrator for permission, then try again. |
| Anchanto OMS is not available on this HexaSync gateway yet | The details you entered are not wrong. Anchanto OMS is not turned on for the HexaSync gateway yet. Send the Technical details to support@beehexa.com. |
| The HexaSync gateway hit an error while checking your token | The gateway hit an error during the check, and nothing has been saved. Try again after one minute. If the error remains, send the Technical details to support@beehexa.com. |
| Another message, with a checklist for Environment, Store code and Token | Anchanto or the gateway did not accept the details: the environment is not valid, details are missing, the Anchanto server could not be reached, the token was rejected, or no store was found with this SMP Code. Check the environment, the SMP Code and the token in turn, following the list below. |
| HexaSync Could Not Link The Credential To Your Connector | The credential was saved but could not be linked to the Connector. The screen lists the values that were sent so you can compare them. Select Go to Manage Credentials to link the credential manually. |
For other cases, send a screenshot (with the token hidden) to support@beehexa.com.
Check these first
- The right environment: a token issued for Production does not work on Staging, and the reverse is also true.
- SMP Code, not store code: HexaSync sends this value to Anchanto under the name
ss_code. The error screen shows the exact value HexaSync sent so you can compare it. - Complete token: paste the token again, with no spaces or line breaks. If Anchanto has reissued the token, the old token no longer works.
- One store, one environment, one credential: if someone else has already connected the store, ask them to share the credential instead of connecting again.
- Safe to retry: connecting the same store and environment again only updates the existing credential and does not create a duplicate.
Part 5: Frequently asked questions
What data does HexaSync get from Anchanto OMS?
HexaSync reads the product and inventory data of the store with the connected SMP Code, within the access that the Anchanto token allows.
Does the Anchanto token expire?
The Anchanto token has no expiry, so HexaSync does not need to refresh it periodically. If Anchanto revokes or reissues the token, update the token by following Part 2.
Where is the token stored?
The token is encrypted and stored on the HexaSync gateway. It is not stored in the browser and is not shown again after you connect.
How do I connect several Anchanto stores?
Each connection covers one store on one environment. Repeat the process with the SMP Code of the other store. If the stores belong to the same OMS account, you can use the same token.
Does HexaSync write or change data in Anchanto OMS?
No. The Anchanto OMS Connector App only reads data. It does not create or update data in Anchanto OMS.