4.94 Release Notes

Some exciting changes to kick off 2017! Having updated our marketing website at the end of last year, we're now beginning to roll some of the look and feel into the software. Besides the many under-the-hood performance improvements, we've also added some new features we're sure you'll find useful. 

Brightpearl rebrands!

You may notice a few visual changes to Brightpearl following our rebranding - we hope you like the new look! 

New discontinued product status

We have created a new status for discontinued products. Previously you could only archive products once all the stock had sold. Now, if you mark products as archived and it has stock, it will move to the new discontinued status. Products with this status will be hidden from purchases and the low inventory report but will still be sellable until all the remaining stock has sold. Once that happens, the product will become archived.

Previously if you did a stock correction or return for an archived product, the status would return to live when given stock. Now, it will be set to discontinued until the stock has cleared. Once cleared it will be returned to archived. Only updating the status manually will change archived or discontinued products to live.

If you wish to batch discontinue items, choose to Batch Archive - this will archive those with no stock and set to discontinued any products with stock.

2017-01-12_151237

The product record does have an option for status, which now also shows this discontinued status.

Batch purchase orders (BETA - available on request)

We have created a new batch Purchase Order pop-up. Previously, the options were limited to a few pre-baked recipes. Now, you can configure each element of purchasing, doubling the number of options you have. We have made this change on the basis of there being two use cases: those who wish to purchase for future sales based on the selected sales, and those who wish to purchase items needed to complete the fulfilment of the selected sales. Once you've done this, you can choose whether to factor in on hand or in stock items, and items already on purchase orders.

2017-01-12_151325

This beta feature is available on request - please contact design@brightpearl.com if you wish to try it out.

Amazon: update channel settings so user can choose Payment Method for Customer Payment

Since we introduced Payment Methods last year, we’ve been updating sales channel settings to choose the payment method rather than the bank account to be used for payments. In this release, we’ve upgraded the Amazon channel.

2017-01-12_151335.

Amazon: visibility of Seller Fulfilled Prime orders

We have added a new setting to Amazon where you can set a status for Seller Fulfilled Prime orders. If you don't want the current behaviour to change, leaving this field blank will do that.

2017-01-12_151305

Sales analysis by reporting category

A new report called Sales by Reporting Category has been added to the sales analysis reports. Sales for products with No reporting category are filtered to None under the category column on the report.

2017-01-12_151343

Short barcode widget for Goods Out notes

We have added a new widget that renders a barcode containing solely the numbers within the goods out note id, without any leading zeros. You can use this on your packing note templates with _gnShortBarcode_. For example, a Goods Out note with ID 123 would scan as '123'.

The current barcode widgets for Goods Out notes adds leading zeros to produce a longer barcode format. Using the same example with the pre-existing barcode widget would scan as '000000000123'.

Change to outbound webhooks

We're in the process of rolling out an improvement to our outbound webhooks, specifically how retries are handled. This will be an opt-in feature, configurable through the API. The feature will become available in the coming weeks, watch this API documentation page for more details.

With the change enabled, the following will apply:

  • We will always attempt to honour registered webhooks and will retry for up to 48 hours to allow for temporary outages in your network or server configuration issues.
  • Any result other than a successful 2XX HTTP status code will be considered a failure, this includes timeouts at the network level.
  • Any 4XX status code will be considered a permanent failure and prevent further retries for the event.
Have more questions? Submit a request

0 Comments

Article is closed for comments.