New Features
Feature 1: Integration with Hubspot
Impact area: New DEAR Integration – Hubspot.
Introduction: DEAR is happy to announce its new integration with Hubspot. Knowledge base documentation coming
soon.
Functionality:
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.
Pre-conditions: None.
Feature 2: Production Module Improvements
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:
- Production BOM – Unit of Measure field: A new read-only field, Unit,
has been added to the Production
BOM component/resource lines. For resource lines, the field will be auto-filled with ‘N/A’. For
component lines, the Unit of Measure will be taken from the component’s product details. - Production BOM – Import/Export of Production BOM: Production BOM can
now be created or updated for an existing product using the Import CSV file function. All existing Production
BOM information can also be exported in CSV format. - Production Order – Add totals to order: The summary of total costs for
the whole order is now displayed at the bottom of the Production
Order screen. - Production Order – Display and print comments from Sales Order: When a
Production Order has been created from a Sales Order, Comments from the Sales Order will automatically be
entered into the Comments field of the Production Order. This does not apply to consolidated Production Orders. - New fields are available for the Production Order printing template:
- SaleOrderMemo – if Production Order is created from Sales Order (not
applicable for consolidated orders) - ProductionOrderComments – the data added into the Production Orders
comments field. - Production Order – Edit Actual time when operation is completed:
‘Production – Edit Completed operations permission’ has been added to the user permissions list. Users with full
access to this permission can edit the Actual time of a completed production operation in the case that it
differs from estimated time. - Reporting: Production finished goods now show on the Finished
Goods Analysis report.
Pre-conditions: None.
Feature 3: Shopify – Order Import Retry
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.
Pre-conditions: None.
Feature 4: New Account Mapping option: WIP account
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.
Pre-conditions: None.
Feature 5: eCommerce Integration enhancement – Auto-assembly setup
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.
Functionality:
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:
- For ordered quantity: Does not check stock quantity. Current
auto-assembly eCommerce behaviour. An assembly order is created for the quantity specified in the sale order,
regardless of stock availability. - For minimum quantity required for picking: Assemble stock required to
meet the quantity of specific sale order. - If stock availability is negative, auto-assembly will produce a finished goods
quantity which is more than the quantity ordered through sale order. - If there is already stock available in inventory but not enough to fulfill the
sale order quantity, auto-assembly will assemble the difference in quantity needed to meet the sale
order requirement. - If stock availability exceeds sale order quantity, auto-assembly is not
triggered.
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.
Pre-conditions: None.
Feature 6: Option to show ‘All COGS’ added to transactional sales reports
Impact area: Reporting module – Customer
Orders by Product Report, Sale
Credit Notes by Product Report.
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.
Functionality:
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
Pre-conditions: None.
Feature 7: Option to show all Journal Costs added to Purchase Cost Analysis report
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.
Functionality:
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.
Pre-conditions: None.
Feature 8: Redesigned forms for Shipping Services, User Profile, and Dropship Purchase
Impact area: User Interface
Introduction: The ongoing UI updates have now been rolled out to the Shipping Service, User Profile and Dropship
purchase screens.
Pre-conditions: None.
