Version 19

×

19.2

19.1

19.0

System Requirements Version 19

19.2

Bug Fixes - 19.2.48 - Released 4 June 2024

This build has the following bug fixes implemented: 
Fixed
11875998 - Update UPS API Call To Support OATH 2.0
UPS is deprecating access key authentication in favor of an OAuth 2.0 security model for all APIs as of 5 August 2024, at which point access keys will no longer be supported for authentication to any UPS APIs. As a result, we implemented a critical fix to our existing UPS freight account functionality to ensure it continues to work. We no longer need any of the information previously required; instead, there is now a button on the UPS freight account page that will send the user to UPS to authorize BirdDog to access the data. Authorization then takes you to the BirdDog home page and upon logging in with the email address we have on record, your system is fully authenticated and you are redirected back to your site. Apart from this, UPS rating is unchanged in BirdDog.

Back to Top

Bug Fixes - 19.2.45 - Released 30 November 2023

This build has the following bug fixes implemented: 
Fixed
11843649 - New Address On Checkout Broken
During Ecommerce checkout, the option exists to create a new shipping address on the checkout page. Before this build, when you created a new address, the popup was not automatically closing after the address was saved, the address list was not removed after the popup was manually closed, and the new address was not saved to the correct table.
Better
11850125 - Convert to Google Analytics 4 (GA4)
Google replaced their existing Universal Analytics with Google Analytics 4. As of 1 July 2023, Universal Analytics stopped processing new hits. As of this build, we support GA4. Instructions for use can be found here.
Fixed
11856578 - Shopify Connector Not Downloading Order Lines Without Product Information
When downloading some subscription orders from Shopify, the connector was registering the order lines as deleted and was not downloading the order (since it was only a 1 line order).
Fixed
11859025 - Send to Service Pro Box Not Behaving Correctly
When a Sage 100 order had the 'SendToServicePro' box unchecked and there was no Service Pro connector setup, the connector sub-system correctly sent the orders to BirdDog. If a Service Pro connector was set up after the orders were already in BirdDog with the 'SendToServicePro' set to '0', the connector was still uploading those orders to Service Pro even though it wasn't supposed to.
Fixed
11863058 - AvaTax Error on Upload to Service Pro
Observed an ugly error when populating data to a new Service Pro instance stating that the AvaTax method or operation is not implemented.

Back to Top

Bug Fixes - 19.2.39 - Released 28 April 2023

This build has the following bug fixes implemented: 
Fixed
11857808 - M1 Connector Doesn't Handle Contacts With Multiple Email Addresses
Prior to this ticket, the connector sub-system would fail if it ran into multiple email addresses on a single contact, a scenario that is perfectly legitimate with M1. Now we download the first one and report the others as a warning.
Fixed
11858277 - Invoice Line Comments Not Downloading
This was happening when using the connector for Sage 100; order line comments were being downloaded, but invoice line comments were not.
Fixed
11858502 - Invalid License Error When Out of Database Licenses and the Local License Has Expired
Improved the error message to better explain what was going on.
Fixed
11859498 - Amazon Connector Not Deleting Failed Item Linkages Correctly
When the Amazon connector reports that an item failed to upload, the item linkage is supposed to deleted. Prior to this build, it was instead failing with a very ugly error.
Fixed
11860712 - Magento Connector Events Example Is Wrong
Removed some incorrect information from our example Magento event that was causing it to fail.
Fixed
11860828 - Site Allow Entry of More Users Than Licensed For
The web software allowed user creation even if the max users were already at capacity. This led to the site becoming nonfunctional.
Fixed
11861753 - Guest Checkout On Ecommerce Does NOT Handle Sage CusNos Correctly
In an Ecommerce system using a Sage 100 environment, when the Guest Customer is set to use a Sage formatted customer - 00-[CUSNO], for example - the Checkout page did not actually log you in as a Guest Customer.

Back to Top

Bug Fixes - 19.2.30 - Released 27 February 2023

This build has the following bug fixes implemented: 
Better
11857632 - JobMaster Not Refreshing License
Job Master was not written to refresh a customer's license. It was assumed that running Enterprise or Enterprise for Windows would do this. This does not work for fully automated customers that only run Job Master so we added the ability with this enhancement.
Fixed
11859510 - Reported Production Integrator Fails With NULL Error
Using Enterprise for Windows | Utilities | Integrators | Report Product was completely broken and simply wasn't working at all. This fixes that.
Fixed
11859554 - Website Doesn't Honor Site Settings Order Defaults
On Site Settings | Order Defaults on a BirdDog Ecommerce website, there are options that can be populated that will automatically add information to an order such as Shipping Instructions or generic User Fields. An error had been introduced into the code so that new orders were not writing information from this site setting to the order in the database.
Better
11858738 - Add ItemFormWide item layout
This adds a new item layout that incorporates any existing fields on the item. To properly utilize this, the item must have populated Item fields. You can then set this Content by editing the Item in the website, navigating to Page Information, and manually setting Content Layout to ItemFormWide. Alternately, if you wish to use this layout globally on your website, you can navigate to site settings | Ecommerce | Other and set the Default Item Template to ItemFormWide. An example of this in use can be found on our demo site here.
Fixed
11859863 - Job Master Doesn't Use License From Config
While testing 11857632 above, we determined that Job Master wasn't properly honoring license information from the existing config file. If the information was blown out from the BDSettings table in an existing database, it had to be manually added back in. Now, when the service runs again, if the license is properly setup in the config file, Job Master will look at that file and update the BDSettings table with this information.

Back to Top

Bug Fixes - 19.2.21 - Released 7 February 2023

This build has the following bug fixes implemented:
Fixed
11854162 - Obsolete Item Flag Not Being Synced To SvcPro
When an item is set to Inactive/Obsolete, we were not sending that flag up to Service Pro. This was allowing that Inactive item to added to an orderline in Service Pro. If we manually set the Obsolete flag on the item in Service Pro, the next time we sync that item up to Service pro, we blanked the flag and unchecked the Obsolete box on the item in Service Pro.
Better
11856005 - BirdDog Pushing Changes to New M1 Ship Tos
  • We now write Country Code to M1 Customer/Ship To country and countryCode fields. Prior to this, we wrote country name to country and country code to countrycode.
  • We also updated to the latest change tracking to remove an upload back to M1 after the initial download (frequently referred to as a "bounce") of a ship-to. Ship-To values that come from the customer (cmlCustomerCreditLimit, cmlCreditHold, cmlCustomerTaxable, cmlTaxExemptNumber, and cmlCurrencyRateID) are only written on inserts (not updates).
  • Finally, we added two new M1 Events: ShipToInserted_Before and ShipToUpdated_Before.
Fixed
11858401 - Add Sales People To Sales Order Upload
Fixed the mapping of the sales person in the Sage 100 connector.

Back to Top

New Features

This branch has the following features implemented: 
Better
11839516 - Customer Type in Service Pro Overwritten to Default
This adds support for syncing customer types to Service Pro. Because this didn't exist before, existing customers will have customer types on ServicePro that do not exist locally. NOTE: This will require a minor data conversion on the Service Pro for existing users, which requires coordination with MSI.
Better
11848775 - Update Enterprise Print Acknowledgement To Use The Crystal Report
Previously, we used email templates which are not as sophisticated as Crystal Reports.
New
11853189 - Combo Picker UDF Not Uploading to Service Pro Correctly
This adds support for "Combo Picker" custom fields in Service Pro. In BirdDog, we don't have a special field type for this as we support a values list on any of the field types. Since Service Pro considers the "Combo Picker" to be a string field, we added our support to our String field type. With this enhancement, if a String field type has no values, we upload it as a Text Input/String field type on ServicePro like we always have. However, if it has 1 or more values then we:
  • Create a matching field on ServicePro with a "Combo Picker" field type
  • Create a Custom Field List on ServicePro naming it with the format "{Field Name} List"
  • Add all of the field values to the previously created list
NOTE: Once a custom field has been updated from BirdDog to Service Pro, we won't change it so if you create a String field in BirdDog with no values, it will be uploaded as a Text Input/String to Service Pro. If you then add values to this field in BirdDog, it will NOT be changed to a "Combo Picker" on Service Pro. You will instead need to delete the field on Service Pro and it will then be re-created as a "Combo Picker" on the next connector run. This behavior is intentional to prevent accidental data loss on the Service Pro side.
Better
11853788 - Add AR_Customer_bus to Sage Query System
Added AR_Customer_bus to the Sage 100 query. Additionally, added improvements to error reporting.
New
11855371 - Add Support For Available To Promise To GraphQL
Added availableToPromise property to the ItemLocation type in our GraphQL API. Also updated the GraphQL Item.defaultLocation property to support anonymous queries and fixed an issue where the anonymous customer wasn't being used for price calculations when not logged in.
Better
11857096 - Add TaskId and ContactId Properties to GraphQl TimeSlipSearch Query
Enhancements to our GraphQL API. Added the following:
  • timeSlipSearch: added taskId and contactId arguments
  • TimeSlip type: added user, status, and durationHours properties
  • Added taskCategorySearch
  • Task type: added userId/user, startTimeSlip, estimatedHoursRemaining, taskCategoryId, dueDate, actualDurationHours/actualDurationText, lastUpdate/lastUpdateBy, and updated creation properties to standard names
  • Project type: added path and updated projectId/projectReferenceNo to be consistent
Better
11858094 - Add Better Handling of Invalid Paths to the Sage 100 Connector
Add checks for the path being valid and for the pvxwin32.exe file being available for the Sage 100 connector. Before the connector will even run, it now validates that the path is valid and that it contains the pvxwin32.exe file that Sage 100 uses to execute. If the path is not valid, it will be more explicit about what the nature of the error actually is.

Back to Top

19.1

Bug Fixes - 19.1.49 - Released 7 February 2023

This build has the following bug fixes implemented: 
Better
11833495 - Remove References to Ship To From The Address Book
When a customer was logged into the site and navigated to their account's address book, we erroneously made multiple references to "Ship-Tos" instead of addresses.
Better
11836975 - Add Support For Schema Fields URL, Review, SKU, PriceValidUntil, and Brand
Improved the item page for Google Search validation purposes. Customized itemform pages will need these fixes applied to their page.
Fixed
11841417 - Clicking on Back to Top on What's New Page Goes to Main Web Page
When going to a page using CATEGORIES layout, like our What's New page, clicking on the Back to Top took you to the main page of the website instead of the top of the page.
Fixed
11846225 - Web Order History Status and Order Form Status Data Doesn't Match
When viewing Order History on the web, the "Status" field on the Order History page didn't match the "Status" field on the Order Form page. While troubleshooting this, we later discovered that it appears that the Order History page was pulling "Status" from OrderTypeMSG. The Order Form page was pulling "Status" from Order.Status.
Fixed
11848769 - Contact With Long Name Won't Create Customer
When adding a contact in BRAIN, if the contact was set to Organization and had more than 40 characters in the name, Enteprrise was choking when you tried to create a customer.
Fixed
11851956 - Amazon Connector Not Pulling Down Shipping Charges on Orders
When using the Amazon Connector Sub-System, freight generated on an order on Amazon was incorrectly coming down to BirdDog as blank.
Fixed
11854001 - Categories Page Using Search Permission Instead Of View
An item with only View permission was not showing up on the Categories.aspx page but did show up on other Categories pages. It also did not show up if the Search permission was enabled. While troubleshooting, we determined the Categories.aspx page was using incorrect permissions when determing what was visible and what wasn't.
Better
11854929 - Ship To Code Too Long Errors
Ship-To codes are different lengths in different ERPs. This project updates Ecommerce to honor the ship-to code length of the ERP it is running against.
Better
11855090 - Enterprise for Windows Could Not Load Invoice Report Pointing to Deprecated Location
While trying to invoice an order, Enterprise for Windows was throwing a 'could not load invoice report' and then referenced a path to change it in the software that no longer exists.
Fixed
11855102 - Error On Email Confirmation Window On Order View
When trying to send an email confirmation email in order view in Enterprise and using Macola ES, the system was throwing a 'Property Ord_No Is Ambiguous On Type BirdDogES.Order' error.
Better
11855884 - Price at UOM Ratio Is Outside The Allowed Range
This error was caused by some old price error handling that set the price to 999999999.9999 when there were invalid item locations. Update to set the price to a valid/in rage value of 9999999.999999. As a result of this fix, there are some changes to how we download/upload orders to ServicePro. When we download an order, we check the following and if either is true, we mark the order to uploaded back to ServicePro:
  • Is Sync Order Line Unit Price not set and the unit price downloaded from Service Pro doesn't match BirdDog OR
  • Is Sales Tax Connector licensed AND (the order is new OR sales tax changed for the BirdDog order based on the changes we just downloaded from Service Pro).
Fixed
11855596 - Site Crash When Changing Time Slips
When changing timeslips in BRAIN using the dropdown list or by starting a new one, the site crashed with a broken rule concerning TaskID.
Fixed
11856362 - Error on Site Load
Resolved an object reference not set to an instance of an object error.
Fixed
11856449 - Sales Order Doesn't Allow 0 Percent Split When Sales Person Set
When we fixed 11847238 in 16.1.25, we added rules requiring that the salesperson split must be set when the salesperson is set. This is not true. This removes that rule. So now it is legal to set sales person #1 to 100, the split for salesperson 1 to 0, sales person #2 to 200, and the split for sales person 2 to 100. The 3 splits must still add up to 100%.
Fixed
11856914 - Errors on Collect Account No Info on Order Entry Screen
When using 'Collect' as the Freight Pay Method on the Order Entry Screen in Enterprise, if you loaded a 'Collect Account No.', then selected a different Shipping method you got an 'Invalid Customer Freight Account' error on the dropdown list. Also when selecting a Collect Account No, there were duplicates on that same DDL.
Fixed
11856942 - Weird Behavior on Add/Edit Freight Account Window in Order Entry
When adding/editing freight accounts on the order entry screen, a window pops up. When you clicked on the top of the window to move it, it shifted down. This was just plain irritating.
Better
11857201 - CC Expiry Limitation
When entering a credit card on checkout page our dropdown list for the card, the expiration date only went ten years. Extended this to eleven years.
Better
11857171 - Zero Qty Ord Line Changes to One After Syncing in Sage
When we originally implemented Sage 100, we did not support quantity ordered of 0 so the Sage connector updated zero to 1 when syncing orders. This adds support for adding lines with qty ordered = 0 in Customer Service when running against Sage 100 or QuickBooks Desktop (since they also allow this). Other ERPs will still display an error message.
Fixed
11858194 - WooCommerce Orders With Variant Items Not Syncing Down With Proper Item Numbers in ERP Order
When an order that has a variant item on it was generated in WooCommerce and connectors were run, the order was incorrectly bringing down the master item instead of the variant. This presumes that the variant items have been correctly mapped.

Back to Top

Bug Fixes - 19.1.27 - Released 30 September 2022

This build has the following bug fixes implemented: 
Fixed
11847021 - Able To Place Order Without Choosing A New Shipto Address
Orders created by an Ecommerce user where an alternate saved shipping address was selected were not generating with this correct address, which made receiving items difficult.
Fixed
11851956 - Amazon Connector Not Pulling Down Shipping Charges on Orders
When using the Amazon connector, freight charges were not coming down correctly to the local ERP.
Better
11853509 - Country Location Does Not Handle Quotation Marks In Name
Unusual scenario where the original ERP environment being utilized had apostrophes in the order address. BirdDog wasn't handling that correctly when pointed at it.
Fixed
11853767 - M1 Connector Won't Delete Jobs That Have Been Released
Fixed an issue where if the job was released and then deleted in M1 it did not get deleted in BirdDog.
Fixed
11854134 - Remove View Invoices In Enterprise for Windows
This functionality has been removed entirely from Enterprise for Windows. Note: Be advised that if you run older code against the database after this has been removed, the older code will add it back.
Fixed
11854294 - M1 Connector Not Handling International Data Well
Customers with non-US countries in M1 were getting changed to the United States in the course of the connector run. Essentially, country codes in M1 have considerably larger field lengths than the core BirdDog engine is accustomed to, so the connector was presuming the information being downloaded was wrong and in the process ended up defaulting back to US. Now it throws a warning and skips that customer.
Fixed
11854986 - Posting Not Setting All Fields On The Header And Line correctly
When posting an invoiced order in BirdDog and comparing it to a posted order in Macola, we were noting some inconsistencies with OE Header History and OE Line History tables.
Fixed
11855142 - Sage 100 Timestamp Not Being Set On Legacy Sales Orders Causing Sync Loops
In an earlier version, we added an optimization to track changes on the Sage 100 side of the connector to keep from downloading when we didn't need to. There was a logic error in this code that caused some issues with changes that appeared in more recent versions. These issues created a scenario where a customer upgrading from an earlier version using a current version of our software could experience a download loop if they were using more than one connector and changed an old sales order.

Back to Top

New Features

This branch has the following features implemented: 
Better
11846560 - Add Support To Choose Which Order Statuses We Download From Woo
This adds a comma-separated list of order statuses to the WooCommerce connector screen. Only orders with a status that match something in this list will download. Orders with a status that does not match will be reported to the log. This also fixes order downloads not using a change date and downloading, but not processing every order from woocommerce on every run. And finally, this fixes item downoads not using the change date correctly and downloading, but not processing every item on every run.
Better
11847472 - Sage Connector Downloading Tax Schedules Every Run
Sage 100 doesn't have "last update date/time" properties on Tax Schedules and Codes so we have no idea when they changed. Prior to this enhancement, we would download them on every run and compare them to what we have. For most customers, this happens fast enough that no one notices. This enhancement adds BDConnectorAccounts.TaxInfoDownloadWaitMinutes. There is no interface for this value because we normally do not anyone messing with it. If this value is set, then the connector will wait that many minutes before downloading Tax Schedules/Codes again. Instructions for setting this up can be found here.
New
11848657 - Add New Setting To The WooCommerce Connector That Controls Handling of WooCommerce Guest Orders
Added a new setting to the WooCommerce connector. In addition to Next Customer Number and Guest Customer Number on the dropdown list for Guest Customer No, we've added "Guest Customer Number With Ship To." Using this will still require the guest customer number to be added in the connector setup, but the system will now add a ship to to the customer for each new guest customer on WooCommerce. When adding a new ship to the system searches the guest customer for a ship to that has a matching email address. If one is found then it uses it. If one is not found it adds the next ship to number (starting at 1000) and sets the address to the ship to address of the order.
Better
11849893 - Add Interface to Shopify Connector to Select What Item Data to Upload
With this build, you can amend the level of item data you wish to push up to Shopify using the connector sub-system.
Better
11850375 - Set Items As Obsolete When Effective End Date Is Set In M1
Added mapping for M1 Part Revisions Effective End Date to Activity Code and Date. If the Effective End Date is set in M1, then we mark the item as obsolete and set the activity date to the Effective End Date.
Better
11852374 - When Requested Ship Date On Sales Order Header Is Changed, Lines With A Matching Date Should Change
This changes the default behavior of the order/cart object. When changing the default shipping date on the header, any lines with a matching request date will be updated as well. Prior to this, the shipping date on the header was only used as the default request date on new lines.
Better
11852746 - Add Standard Shipping Days To The ATP Calculation
Added "Standard Shipping Days" to the Manage Picking page on Warehouse Management which defaults to zero. Whatever value is plugged into that is then added to the Available to Promise (ATP) calculation.
Better
11853061 - Add Picking Sequence Column to Item/Location Import Template
Improved the existing import.
New
11853224 - Sage 2022 Compatibility
As of this build, our connector sub-system is fully compatible with Sage 100 2022.
New
11853690 - Enhancement To Add JobMaster Support For Purchase Order Integrator
BirdDog has long supported an interactive import of Purchase Orders using Enterprise for Windows. This enhances that process to support automatically reading files from a directory with Job Master.
Better
11853596 - Set Items As Obsolete When Inactive Is Set In M1
Added mapping for M1 Part Revisions Inactive flag to Activity Code and Date. If the Part Revision is marked inactive, then we mark the item as obsolete and set the activity date to the Effective End Date; if Effective End Date is not set, then we use today's date.

Back to Top

19.0

Bug Fixes - 19.0.10 - Released 19 September 2022

This build has the following bug fixes implemented: 
Better
11847501 - Tax Exempt Number Field Not Passing between BirdDog and Sage
A new customer created in Sage 100 with a tax exempt number was not syncing up to BirdDog with that number the appropriate table. If an customer was generated in BirdDog or a different system (like Service Pro) with a tax exempt number and synced down, it would bring that number down to Sage, so this was only an issue going one way. Additional information regarding setup for this can be found here.
Fixed
11851850 - ConfirmTo Field In Sage100 Gets Overwritten When Syncing Order To SvcPro and Back
This bug was discovered following a specific scenario: an order was generated in Service Pro, synced down to Sage 100 and then adjusted by adding new data to the 'Confirm to' field there was not syncing back up to ServicePro with that information. Further, this required both connectors to be enabled as if they were run one at a time - so one is disabled until after the connector was run, and then it was disabled and the other was enabled for a second connector run - this worked fine, so it was clear that the data was stepping on itself.
Better
11852476 - Cart.Ordered By Name is Defaulting to Customer.Name on Shopify Orders
On an order downloaded from Shopify, the Cart.Ordered_byname was defaulting to Customer.Name and should have been defaulting to Customer.Contact. Our fix low involves a level change to how the Cart functions which changes the way OrderedBy info (name,email,phone) gets defaults. This removes scenarios where ordered by name default to the customer name. It also removes any defaulting of OrderedBy info when the User has the customer service role.

Back to Top

New Features

This branch has the following features implemented: 
New
11843367 - Add Order.Applying and Applied events
The behavior of the custom event Order.Placed has changed. You are now required to call ApplyEdit on the order if you make any changes. This is a breaking change.
Better
11843764 - Sync More Fields Two-Ways With ServicePro Customers and Orders
Improved syncing for Customers, Ship-Tos, and Sales Orders when using the connector sub-system for ServicePro environments.
Better
11845345 - Upgrade Crystal Reports
Upgrades our systems to use Crystal Reports 13.31.
Better
11846951 - Move SendEMailConfirmation From Web Down To Cart
This is a development change that leaves existing behavior unchanged for email confirmations on new orders from ecommerce and customer service. This also adds a new job "Convert a cart to an order" that allows you to process a single cart to order.
New
11850404 - Support Writing Credit Card Cash Receipts to Sage 100
We added the ability to capture credit cards for Sage 100 Ecommerce customers in 11846176 Auth Card In The Ecom Site And Capture When Invoiced in External ERP released in 18.1.14 when invoiced in Sage 100. This project completes the accounting loop for those transactions.
Better
11851694 - Sage Item Extended Description Not Pushing Up To BD Correctly
Extended the item description field length throughout the system to 4096 for Sage 100 to enable support for extended descriptions. Updated the Sage connector to use the extended description, if it exists, for items, sales order lines, and invoice lines.
Better
11852767 - Invalid Project Code Error Downloading Orders with a Job Number From Sage
This branch adds the "auto-adding" of missing projects when downloading from Sage 100. Job Number was Sage functionality that we'd missed in previous versions of the software because, until recently, none of our clients actually used it in their Sage environments.

Back to Top

Reason for Point Release

This point increase (v18 to v19) was principally caused by three projects: 11845345, which upgrades BirdDog code to handle Crystal Reports 13.31; 11843367, which modifies the behavior of the custom event Order.Placed; and 11851694, which greatly extended the item description field length.

Back to Top

System Requirements Version 19

Server Requirements

Software Requirements
BirdDog Software can be deployed on a dedicated or virtual server that meets the following requirements:

Minimum hardware required:
  • Windows 2008 R2 Server
  • Minimum: 8 GB of RAM, recommended: 16 GB of RAM
  • Minimum .Net Framework 4.7.2
  • 300-500 MB of available hard disk space per installed instance of BirdDog
BirdDog software can be installed on both x86 (32-bit) and x64 (64-bit) versions of the following:
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019
Database Server Requirements
Hardware requirements:
  • Minimum: 8 GB of RAM, recommended: 16 GB of RAM
  • 200 MB of available hard disk space. Depending on the number of transactions, additional hard disk space may be required to store large number of transactions.
  • Document Management, additional hard disk space depending on the amount of documents. 5GB of documents will require 5GB of additional storage. Consider this, Using an estimate of 2,500 pages per file drawer and four file drawers per file cabinet, one can estimate that scanning two four drawer file cabinets full of documents (ten thousand single sided pages) will require 1 GB.
The BirdDog database can be hosted by:
  • Microsoft SQL Server 2012, any edition
  • Microsoft SQL Server 2014, any edition
  • Microsoft SQL Server 2016, any edition
  • Microsoft SQL Server 2017, any edition
  • Microsoft SQL Server 2019, any edition

Full-Text Search needs to be installed on your SQL Server for our software to function correctly.

Back to Top

Work Station Requirements

  • 2gb of RAM
  • 2GHZ or better CPU
  • High speed internet
  • Windows 7 or later
  • If using Avatax, 64-bit is required

Back to Top

Web Browser Requirements

Web-browser Requirements for Ecommerce
Our publicly facing system can be accessed by any device with one of the following browsers:
  • Microsoft Internet Explorer version 9.0 or later
  • Mozilla Firefox version 10 or later
  • Apple Safari version 6 or later
  • Google Chrome version 17 or later
Web-browser Requirements for Enterprise
Our ERP system can be accessed by any device with one of the following browsers:
  • Microsoft Internet Explorer version 11
  • Mozilla Firefox version 10 or later
  • Apple Safari version 5 or later
  • Google Chrome version 17 or later

Back to Top

Receive your free product tour!

Need Help? Have Questions?

Industries

Find out how BirdDog Enterprise fits your niche!