Account
Cart
(
0
)
Login
(
0
)
Products
BirdDog Ecommerce
Tools
Integrations
Connectors & Feeds
Solutions
Ecommerce
B2B Ecommerce
B2C Ecommerce
D2C Ecommerce
Sales Order Management
Online MarketPlace Feeds
Credit Card Processing
CRM
Manufacturing
Banking
Front Office
Back Office
Warehouse Management
Ecommerce ERP Integration Software
ERP Integration
Macola
Quickbooks
Sage 100
Infor
Epicor
M1
Other ERPs
Services
Company Website
Corporate Identity
Website Design
Website Content Migration / Population
Strategic Marketing
Content Management & Marketing
PPC Pay Per Click Ad Management
E-Mail Hosting
Web Server Monitoring
Software Training
Custom Software Development
Support
What's New
Product Documentation
Software Installation
Training Videos
Support Policies and Services
SQL Server - Microsoft
Company
About BirdDog Software
Our Team
Contact Us
Intern in Software Development
Privacy Policy
BirdDog Careers
Partnership Opportunities
Blogs
Support
What's New
Version 9.8
9.8.5
Update Notes
×
6849403 - Implement Credit Card Aliases for Authorize.Net
-
Customer Information Manager(CIM) has to be turned on inside Authorize.Net for this to function correctly. This can be done before starting the update since turning it on will not affect the older software. Basically, go turn it on now. You can view how to accomplish this by watching
this video
. If this is the first time you have used Authorize.net, nothing else needs to be done, but if you have taken orders using BirdDog before, then you will need to run the Credit Cards: Convert Encrypted Credit Cards To Profiles job after all software is running 9.8.5. This process can be started any time after the update is complete. If you test with a staging site against production data do not process any credit card transactions (including authorizations) against production data while production sites are running versions earlier than 9.8.5.
NOTE:
If running a synced site, this process must be run on both the local and hosted side.
7428068 - Implement 3DSI Payment Gateway
-
All valid IPs that are intended to utilize this gateway first need to be whitelisted by 3DSI. Additionally, items must also have UNSPC codes assigned to them; these codes are created in system management and added to items on the item form. A default UNSPSC code should be established (see 8843082 below) and then any items that do not match this default can be given an appropriate code.
8843082 - Added support for United Nations Standard Products and Services Code® (UNSPSC®)
-
A default UNSPSC code should be established. See
https://www.unspsc.org/
for information on the classification system. First, the code must be created - this is accomplished in System Management | Inventory | United Nations Standard Products and Services Code. Once created, navigate to System Managment | Global Settings and plug that code into the UNSPSC field on the Inventory tab.
8963397 - Add Sync Locations and enhance sync reliability
Upgrading sync customers need to navigate to System Management | System | Sync Locations and ensure the remote site has the Next numbers set correctly. This allows you to set the next order number, the next customer number, the next work order number and the next OE cash number for remote sites (in this context, they are usually the "live" site.)
Need Help? Have Questions?
Industries
Find out how BirdDog Enterprise fits your niche!
Retail
Manufacturing (MFG)
Service Companies
Non-Profit
Ecommerce Companies
Distribution / Wholesale
Software Companies
Powered By
BirdDog eCommerce