Impact area: New DEAR Integration – Hubspot.
Introduction: DEAR is happy to announce its new integration with Hubspot. Knowledge base documentation coming soon.
DEAR Integration with Hubspot supports import/export of Products, Customers and Sales from/to Hubspot. At this time, bidirectional synchronisation is not supported.
Sales in DEAR correspond to deal stages in Hubspot – once a deal/sale hits a certain stage, synchronisation will be triggered.
Impact area: DEAR Production Module.
Introduction: The Production module is aimed at addressing the needs of the production process. New production features will provide our current customers with powerful, logical manufacturing solutions to add to their inventory solution.
Following on from our most recent releases, we are continuing to improve the Production module functionality and add features. This release’s new features are:
Impact area: Shopify Integration.
Introduction: Occasionally, during order syncing from Spotify, some sales are not created on the DEAR end. Previously there was no way for a DEAR user to be notified of these failed orders. DEAR developers have now implemented an auto-retry function for sale orders which have not been created in DEAR but are valid sale orders on Shopify.
The new function retries the sale order sync to ensure all sales created in Shopify are also created on DEAR on a daily basis. The Order Import Retry function is enabled from the Shopify Integration setting page and is carried out automatically by the DEAR backend system.
Any errors of failure to load sales through auto retry functionality will be captured in the operations log recorded under the subsequent sale record. Sale orders which fail to load will also generate an internal notification for DEAR users containing sale order details and error information.
Impact area: Production Module, Account Mapping.
Introduction: A new default field, WIP account, has been added to the Account Mapping page. WIP refers to the raw materials, labor, and overhead costs incurred for products that are at various stages of the production process. This account will be filled in as the default WIP account for Production and Assembly tasks.
See Accounts and Chart of Accounts for more information.
Impact area: eCommerce Integrations – Shopify, POS, Vend POS, Magento, Magento 2, WooCommerce, Square, Amazon, Ebay, Etsy, Shipstation.
Introduction: Auto-assembly is triggered when a sale order for the finished good is authorised. Up until this release, for finished goods assembly, the auto-assembly function is triggered for sales coming through all ecommerce channels, even if there are sufficient stocks of finished goods in the inventory.
DEAR customers using eCommerce integrations would like to have the flexibility of managing this setting of auto assembly, to determine if auto assembly should trigger based on the ordered quantity or only assemble based on available stocks in hand.
A new setting, “Process Auto-Assembly” has been added to the settings page of the eCommerce integrations listed above. This dropdown field has two options:
Stock availability is validated against the sale order location and does not take On Order quantity into account.
See Finished Goods Assembly – Auto-Assembly for more information.
Introduction: Transactional sales reports pull entries based on accounting transaction dates. Many of DEAR transactional sales reports have the option to filter pulling entries between “COGS within date range” or “All COGS”. This functionality has been expanded to the Customer Orders by Product Report and Sale Credit Nots by Product Report.
Transactional sales reports pull entries based on transaction dates (if COGS within date range is selected) or invoice dates (if all COGS is selected).
Transaction dates include invoice authorisation, ship tab authorisation (COGS) and payments. For dropshipped products, COGS transactions are triggered when dropship purchase invoice is authorised. If you need COGS to have same date as the invoice, you need to change delivery date same as the invoice date (you can undo the ship tab to do this.)
If only COGS within date range is selected, a) you may see invoice dates from before the reporting period (with COGS transactions within the reporting period) and b) may see some 0 COGS values (if the ship date is out of the reporting period).
If All COGS is selected, the report will pull entries by invoice date, but COGS will be shown regardless of when the ship tab was authorised. If the ship tab has NOT yet been authorised, COGS will be 0
Impact area: Reporting module – Purchase Cost Analysis Report
Introduction: Purchase Cost Analysis report pulls entries based on transaction dates and stock movement dates. This can lead to some entries being left out of the report if the effective dates fall outside of the reporting period. Purchase Cost Analysis report now has a filter “Show Journal Costs” to determine if only journal costs within the date range are shown or all journal costs.
If “Journal Costs within date range” is selected, the report pulls entries based on stock received date. Only transactions (invoice authorisation, credit notes, payments, manual journals) that fall within the reporting period are shown. This is the current functionality of the report and the default option.
If “All Journal Costs” is selected, the report will pull entries based on the Purchase Invoice date, and all transactions on record will be shown, even if they fall outside of the reporting period.
Impact area: User Interface
Introduction: The ongoing UI updates have now been rolled out to the Shipping Service, User Profile and Dropship purchase screens.
Try DEAR for 14 days, completely free!