Field |
Description |
Avalara Admin Login |
The URL to the Avalara site access. |
Avalara API Account Number |
Account number as provided by Avalara. |
Avalara API License Key |
License key number as provided by Avalara. |
Avalara API Operating Mode |
You can select Testing or Production modes to verify the connection. When testing is complete, the mode should be in Production. |
Avalara API Logging: |
The logging function tracks all API hits, which helps with potential debugging or troubleshooting needs. The options are: Latest (default) = tracking of most recent action taken on order, helps keep log size small Committed = sends only transactions that have been finalized All = every API hit is saved None = no API hits are tracked Log details are accessible from an order's Transaction Summary by clicking on the Sales Tax "Details" link. Click here for a sample logClick here for a sample log. |
Default Tax Code: |
From the list of codes generated through your Avalara account, you can select as your default that will be applied to all products. The default tax code can be overwritten at the individual product level or through merchandise hierarchy assignments.(See Product Assignment section below.) |
Avalara SST Member |
Identify if you are part of Avalara's Streamlined Sales Tax program. |
Avalara State Exceptions |
A multi-select list was added for states for Avalara exceptions. Avalara API will not be able to request/commit tax details if the shipping address state lies in the selected list in the 'Avalara State Exceptions' system setting. |
Active Avalara Channels |
|
Perform Connectivity Test |
Press the button to test API connectivity. i.e can I access the API endpoint with the entered information? If not then, re-check that all information has been entered correctly and, failing that, contact Avalara to make sure your account is active. |
Setup to send Purchase Orders by Fax from the backoffice using eFax.com. Required eFax.com account.
Field |
Description |
eFax Email Address: |
Enter the eFax.com email address and then click Apply. The eFax.com integration is now enabled and you can begin sending purchase orders. |
Create New: |
Click 'Create New' to be taken to the eFax.com website where you can create your account. |
Mailgun is used by CORESense to manage the send and receive of emails. When Mailgun is set up you will need to add two 'TXT" records in the public DNS for your domain in order to send emails from that domain. If you are also going to use CORESense for receiving inbound emails, you will need to add (2) MX records in the public DNS for your domain. These records will be provided to you by the CORESense implementation or customer support teams.
Field |
Description |
Mailgun Enabled: |
Whether or not Mailgun is enabled. |
Mailgun Mode: |
Set to Production to send emails, or set to Testing to filter out any emails that are not going to the Mailgun Domain or the Default Domain. |
Mailgun Domain: |
Specify the domain to be used with Mailgun. |
Mailgun API key: |
If you have a direct Mailgun account with your own API Key, you can enter your information in the settings below otherwise this field is left blank. |
Apply Settings
After you have entered all the information for the fields you want to be set, click on the Apply button at the bottom of the table to save your entries. Click on Reset to clear the fields and change your entries.
CORESense has leveraged the Webhook functionality that Mailgun uses to manage bounced emails. This feature will return any bounced emails back to the identified "FROM" email address. Bounced emails were previously only available from the Mailgun control panel Event Viewer. This has been set up for all Mailgun clients who are using the CORESense domain, no action is required, and is set up during your implementation. However, If you have a direct Mailgun account with your own API Key, you can go to your Mailgun Control Panel > Bounces > Webhooks to set up this feature.
Field |
Description |
Power Reviews Enterprise Mode: |
Determines the Power Reviews Enterprise run mode. |
Set up fields in the Journal Entry Export Overview output files. This file can be imported into Quickbooks using TransactionPro.
Field |
Description |
Sales and Payments Transaction Id Number: |
Transaction ID exported for all sales and payments accounts |
COGS and Inventory Transaction ID: |
Transaction ID exported for all COGS and inventory accounts |
Receiver Export Epoch: |
Specify the date after which PO Receivers will be exported (yyyy-mm-dd). |
This feature provides support for the TaxJar sales tax compliance platform.
Field |
Description |
TaxJar API Token: |
Token provided by TaxJar. |
TaxJar API logging |
Determines what if anything is logged. Options included:
|
Default Tax Category |
Sets the default TaxJar Category to use if none is set at the product or merchandise hiearchy level. |
Active TaxJar Channels |
Active - When checked for a channel, enables TaxJar for that channel. Channel - There is an entry for each channel in your back office. Source Warehouse - Set the source warehouse sent to TaxJar for sales transactions. Recommended is to use TaxJar Defaults. |
Support TaxJar Reporting |
Whether or not to push transactions into TaxJar for reporting purposes. The transaction_date is set to the date the transaction is pushed to TaxJar, which is typically when the order has been fully shipped and locked. Enabled, is yes. Disabled, is no. |
TaxJar Tax Exempt |
Whether or not to push tax exempt customers to TaxJar for reporting purposes. Enabled, is yes. Disabled, is no. |
This feature provides the ability to import the full SanMar product catalog into CORESense and then update the catalog on a daily basis. It uses the SanMars FTP and Web Services Integrations.
Field |
Description |
SanMar Customer Number: |
Your SanMar Customer Identification Number |
SanMar Web Services Username: |
Web Services username provide to you by SanMar. |
SanMar Web Services Password: |
Web Services password provided to you by SanMar. |
SanMar FTP Password: |
SanMar FTP server password. |
This feature provides the ability to import the full S&S Activewear catalog into CORESense and then update the catalog on a daily basis. It uses the S&S Activewear API.
Field |
Description |
S&S Activewear Account Number: |
Your S&S Activewear Account Number. |
S&S Activewear API Key: |
Provided by S&S. |
Thomson Reuters as the sales tax service integration.
Field |
Description |
ONESOURCE User Name: |
As provided by Thomson Reuters. |
ONESOURCE Password: |
As provided by Thomson Reuters. |
ONESOURCE Company Id: |
As provided by Thomson Reuters. |
ONESOURCE Operating Mode: |
Production or Testing. |
Default Commodity Code: |
The commodity code to use in none is specified. |
ONESOURCE State Exceptions: | Select the states to NOT USE ONESOURCE for sales tax calculations. |
Active ONESOURCE Channels: | Select the Channels and Warehouse (source) to USE ONESOURCE for sales tax calculations. |
Perform Connectivity Test | This tests that the credentials you have entered are correct and can be used to connect to the ONESOURCE API server. |
PrintNode provide clients with the ability to connect any printer to CORESense application. You can sign up for an account at PrintNode, and then download and install their client software to the PC with the printer attached (i.e., the shipping station computer). Their software runs on Mac, Linux and Windows, and you can print using any browser. You don't even have to be using the computer that the printer is hooked up to.
Once you have an account with PrintNode and the client installed on the PC create an account using the API Key you get from the PrintNode.
PrintNode printers for the PrintNode accounts are available to specify as the default Label Printer IP Address (System Settings Manager > Products / Labels > Label Printer IP Address:) as well as in User Preferences > Default Barcode Label Printers
Label |
API Token |
Clientt defined label |
PrintNode API Token |
© 2023 CORESense · info@coresense.com · 125 High Rock Avenue, Saratoga Springs, NY 12866