Erply API version 1.26.5

22 October 2018

Fixes

Fixed: API call getSalesReport produced an error with input parameter "reportType" = "SALES_BY_ALL_PRODUCTS".



ERPLY Berlin Back Office version 5.13.3

10 October 2018

Improvements

  1. There are now two variations of the Reward Point Balance Report (Customers → Reward Point Balance Report):

    1. “Reward point balances”
    2. “Reward point balances and recent transactions”

    Previously, we only offered the latter option. Due to the extra information displayed, the report was slow to calculate and was also disabled on larger accounts (accounts with more than 200,000 customers).

    The new, simpler view is an alternative that should work well even with larger data sets. Also, “Reward point balances and recent transactions” is no longer disabled on large accounts — but if the report takes too long to load, consider using the simpler option instead.

  2. In Settings → Configuration → Sending invoices by e-mail, email message text can now be defined for all languages.

  3. “Product” table in report generator now contains product names in all languages.

Fixes

  1. Fixed: Sales reports in CSV format had an incorrect “.xls” file name extension.


Erply API version 1.26.4

8 October 2018

Fixes

Fixed: an error in customer and product full-text search.



ERPLY Classic Back Office version 4.12.2

5 October 2018

Fixes

  1. Fixed: on accounts with customer registry integration, popovers in the list of purchase documents did not show supplier name.
  2. One customer-specific rule removed.


Berlin POS version 3.30.1 release notes

26 September 2018

Base version: 3.30.0

Fixes

  • Fix all in one receipt printing from PC (duplicate payment receipts)
  • Hitting F2 while product search is in progress with very slow internet can result in an underpaid sales document
  • TriPOS integration void after unsuccessful multi-card payment and on payment window close
  • Fix Estonian National ID code handling on customer identification


Berlin POS version 3.30.0 release notes

24 September 2018

Base version: 3.29.7

New Features

  • Added Thai language support
  • EPSI download URL and installation instruction by client OS
  • Random weighted products price can be overwritten on order opening
  • Cayan Mini can be turned on/off from payment configuration
  • Added Swedish fiscal integration support (PosPlus)
  • New plugin hook "after_plugins_loaded" for event plugin loaded successfully

Improvements

  • After multi-card payment fails, auto-void is removed from all integrations. Successful payment will be voided on payment window close by user
  • GDPR error handling (Correct API error messages on GDPR related errors)
  • Fix POS side receipts (implemented settings from Back-Office)
  • Allow use POS with browsers, where application cache is not supported

Fixes

  • On PAX iPad, added amount check after payment success to ensure partially fulfilled payments will not go through
  • POS prompts for return reason again when the manual discount is applied to non-receipt return (return reason now always takes precedence over discount reason)
  • Get correct next invoice number on POS select
  • Fix multiline product description display
  • Restore orders pre-paid amount in case document creator is selected manually
  • Fixed discount and return reason behaviors on document discount
  • Fixed identification of the customer by the National ID (Estonian) number


ERPLY Berlin Back Office version 5.13.0 - 5.13.2

17 September 2018

New Features

  1. Email address masking now optional.

    On accounts within the scope of General Data Protection Regulation (GDPR), email address masking (replacing parts of email addresses with asterisks in “Email log” and Calendar → Tasks) is now optional. A new setting has been added: Settings → Configuration → Sending invoices by email → “Anonymize addresses in logs” which can be turned off.

    We advise to turn it off only if emails are predominantly sent to corporate customers, and storing the email addresses in tasks is acceptable according to your company’s data retention policy.

  2. Print a purchase document in any language.

    A “Language” drop-down has been added to the “Print / Send” dialog on a purchase document form. When printing a Purchase Order or Purchase Invoice, or sending it by email, it is now possible to either select the option “Current language”, or pick a specific language.

    “Current language” prints the document in currently selected language, with item names as they have been entered on the document. This might be useful if line descriptions have been overwritten or additional details appended.

    Selecting any other language gives a fully translated printout, with item names taken from product card.

  3. Sales document printout can be configured to show prices with VAT.

    On accounts where all sales documents have been configured to use the “retail calculation algorithm”, an additional dropdown appears in Settings → Configuration → Sales document printouts: “On printout, show: net prices / prices with tax”.

    This option (to show prices on the printout with VAT included) has been requested by Finnish customers.

  4. “Warehouse Report” has been reordered.

    The “Warehouse Report” on product card (list of transactions made with that product, and quantities in stock) has been reordered. Current inventory quantities are now listed first. The list of transactions comes after that, ordered chronologically with newest transactions at the top (not oldest ones at the top, as before).

  5. “Warehouse Report” shows less data initially.

    “Warehouse Report” on product card now initially displays only 100 most recent transactions. The full history can be loaded by clicking a link.

  6. Number of locations configurable in “Warehouse Report”.

    In the “Warehouse Report”, each user can toggle whether they want to see inventory quantities for all locations, or only for the most important ones. A link “Show more” / “Show less” appears as needed. The number of “important” warehouses can be configured from Settings → Configuration → Inventory and purchase, and is 25 by default.

  7. “POS multicurrency” module added.

    This is an extra feature which allows to count the register in Berlin POS in multiple currencies. Please contact customer support to enable it on your account.

    Additionally, customer support must apply configuration parameter"touchpos_sale_additional_currencies" to define which currencies need to be counted in POS.

  8. New report has been added: Reports → Sales Promotions → Promotions By Invoice Report. It displays the same data as Promotions Report, but aggregated by invoice.

  9. Configuration parameter "inventory_report_exclude_archived_products" = 1 has been implemented. When set, Inventory Report will always omit archived products (which may be desirable if the report takes a lot of time, or runs out of memory).

  10. Configuration parameter "disable_automatic_price_from_previous_quote" is now supported on Berlin back office, too. With this parameter enabled, back office and API will not apply prices from customer’s previous quotes. (By default, when you create a sales document, pick a product and the customer has a non-expired quote containing the same product, the previously quoted price will apply.)

  11. On forms where the fields on the sidebar are arranged into groups (with subheadings between groups) the groups can now be collapsed to hide unnecessary fields. Erply will remember which groups are expanded and which ones collapsed, as a per-user setting.

  12. On accounts within the scope of GDPR, helpdesk consultants will no longer be able to access the Customers module.

  13. Product export file now includes the quantities of packaging materials (which can be entered on product card if the respective module has been enabled on your account).

  14. For Estonian customers, a version upgrade notification now displays a link to localized release notes.

Improvements

  1. Support for Thai language has been added.

  2. Support for Faroese language has been added.

  3. Spanish translations have been updated.

  4. When scheduling the tasks on an Assignment, the calendar view that opened when clicking on the “Add”link worked inconsistently. It has been adjusted to work as follows:

    1. If assignment has a location defined, the popup will display location’s calendar.
    2. Otherwise it will display the joint calendar of all user groups designated for repair jobs.
  5. On Actual Reports sales document printouts, a new field is available: each product’s quantity in stock. (Field names are "amountInStock", "amountReserved", and "amountAvailable".)

  6. On Actual Reports sales invoice printouts, the "payer..." and "shipTo..." fields are now always populated, regardless of account settings and regardless of whether the invoice has a separate payer and receiver of goods or not.

    On standard templates, it is recommended to use the "payer..." and "shipTo..." fields, instead of the "customer..." fields. Different accounts may be configured differently, and the semantic meaning of “Customer” may vary; on older accounts, “Customer” typically means the receiver of goods, while on newer accounts, it means the payer.

  7. Actual Reports, purchase document printout: every document row now also includes product pictures.

  8. Field “Location” has been added to “Recurring billing” form. If you specify the location, all invoices created from that recurring billing will be issued from that location.

  9. In product export, product’s net weight and gross weight are now returned in a uniform number format.

  10. On user group form, the permission check boxes “Add shipping” and “Set tax exemption” are now visible regardless of account’s country. Formerly, these fields were activated only on American and Canadian accounts.

  11. Downloaded PDF file names can now contain Russian letters.

  12. Like in Classic back office, table rows can now be right-clicked (to select “Open Link in New Tab”, for example). However, right now there is just one column in every table that supports right-clicking. (This column is indicated by an underline that appears on mouse hover.)

  13. On purchase document form, row height has been reduced to improve information density.

  14. Improvements in report generator:

    1. Column “ID” has been added to all tables.

    2. The error message that appears when trying to group or sort by a calculated column (eg. Sales document → Amount Paid) is now translated.

    3. New columns added: Sales document → Shipment packed by, Sales document → Year and month, Sales document → Payment deadline.

    4. Columns “Year number” and “Month number” in table “Sales document” now allow grouping and sorting.

    5. When grouping the report by a certain value, the value on the subtotal row is now displayed in the same number or date format as the rest of the data.

Fixes

  1. Fixed: when selecting a customer that has been configured as a “EU” or “outside EU” customer, tax rates on sales document are now appropriately set to 0%.

  2. Fixed: when creating a new user, it was not possible to immediately choose which stores the user should have access to. The list of stores only appeared after the user had been saved.

  3. Fixed: when a bundle product was sold through recurring billing, bundle components were not subtracted from inventory.

  4. Fixed: popovers did not appear in the “Purchase Orders” module.

  5. Amount in EEK has been removed from purchase document printouts.

  6. Fixed: Inventory Report now respects configuration parameter"users_can_only_see_own_warehouse_stock".

  7. Fixed: after emailing an unconfirmed purchase order, its status in the list was incorrectly shown as “Confirmed”.



Erply API version 1.26.3

14 September 2018

Fixes

  1. Fixed: a user rights issue in certain API calls, eg. “savePriceList”. (User rights were checked for the wrong module.)


Erply API version 1.26.2

12 September 2018

Fixes

  1. Fixed: when encountering an error while handling a bulk request (eg. no session key provided), API returned an empty result instead of indicating the error code.


Erply API version 1.26.0, 1.26.1

4 September 2018

New Features

  1. Input parameter "searchNameIncrementally" in API call getCustomers now additionally returns customers whose company registry code, or a person’s National ID number exactly matches the specified search phrase.

  2. Compliance with General Data Protection Regulation can now be activated on demand on non-EU accounts, too — with configuration parameter "gdpr_features_enabled" = 1.

  3. Field "reasonID" has been added to API calls saveInventoryRegistration and getInventoryRegistrations.

  4. Input parameters "documentDateStart" and "documentDateEnd" have been added to API call getSalesReport, allowing to filter a Cost of Goods Sold (COGS) Report by document date (as an alternative to filtering by inventory transaction date).

    Please see the documentation for that API call for a more in-depth explanation about the COGS report and date ranges. This feature requires Classic back office, version 4.12 or newer.

  5. API calls getSalesDocuments and saveSalesDocument now support per-row waybill IDs which indicate which row on an invoice has originated from which waybill. API call getSalesDocuments outputs a new field "sourceWaybillID" on each row; saveSalesDocument accepts input parameter "sourceWaybillID#".

  6. Fields "variationDescription" → "order" and "variationList" → "order" have been added to API call getProducts. This allows to sort a list of matrix variations in the same order in which the respective colors / sizes have been arranged.

Improvements

  1. Support for Thai and Faroese languages has been added.

  2. Configuration parameter "api_getpointsofsale_all_invoice_numbers_not_returned" = 1 enables an optimization: API call getPointsOfSale returns the field "lastInvoiceNo" to Berlin POS only if POS asks for one specific register, and not the whole list.

Fixes

  1. Fixed: when creating a new payment with savePayment, API will now populate “last modification timestamp” with current timestamp, not user-supplied data. (Input parameter "added" is still accepted, but it won’t affect last modification timestamp any more.)

  2. Fixed: the checkbox “Customer does not earn new reward points” on customer form was interpreted incorrectly, and API did not allow the customer to spend those points, either. This restriction has been lifted from API calls editEarnedRewardPointRecord, editUsedRewardPointRecord,getCustomerRewardPoints, saveIssuedCoupon and subtractCustomerRewardPoints.

  3. Fixed: When deciding whether to instruct POS to issue a coupon or not, API call calculateShoppingCart ignored the check box “Customer does not earn new reward points” and always assumed that customer is going to earn points from the current transaction, too.



ERPLY Classic Back Office version 4.12.0, 4.12.1

4 September 2018

New Features

  1. Email address masking now optional.

    On accounts within the scope of General Data Protection Regulation (GDPR), email address masking (replacing parts of email addresses with asterisks in “Email log” and Calendar → Tasks) is now optional. A new setting has been added: Settings → Configuration → Sending invoices by email → “Anonymize addresses in logs” which can be turned off.

    We advise to turn it off only if emails are predominantly sent to corporate customers, and storing the email addresses in tasks is acceptable according to your company’s data retention policy.

  2. Print a purchase document in any language.

    A “Language” drop-down has been added next to the “Print” and “PDF” buttons on a purchase document form. When printing a Purchase Order or Purchase Invoice, or sending it by email, it is now possible to either select the option “Current language”, or pick a specific language.

    “Current language” prints the document in currently selected language, with item names as they have been entered on the document. This might be useful if line descriptions have been overwritten or additional details appended.

    Selecting any other language gives a fully translated printout, with item names taken from product card.

  3. Sales document printout can be configured to show prices with VAT.

    On accounts where all sales documents have been configured to use the “retail calculation algorithm”, an additional dropdown appears in Settings → Configuration → Sales document printouts: “On printout, show: net prices / prices with tax”.

    This option (to show prices on the printout with VAT included) has been requested by Finnish customers.

  4. “Warehouse Report” shows less data initially.

    “Warehouse Report” on product card (which shows current quantities on hand, current reservations and all past transactions with the item) now initially displays only 100 most recent transactions. The full history can be loaded by clicking a link.

  5. Number of locations configurable in “Warehouse Report”.

    In the “Warehouse Report” on product card, each user can toggle whether they want to see inventory quantities for all locations, or only for the most important ones. A link “Show more” / “Show less” appears as needed. The number of “important” warehouses can be configured from Settings → Configuration → Inventory and purchase, and is 25 by default.

  6. On accounts within the scope of GDPR, helpdesk consultants will no longer be able to access the Customers module.

  7. “Discount” column has been added to Purchase Orders, and the discount amounts are now preserved when copying a purchase document.

    (Formerly, all other purchase document types had the “Discount” column, only Purchase Order did not.)

  8. On product card, the tab “Replacement products” has been renamed to “Substitutes”, and an additional tab, “Cross-sell” has been added. (Under that tab, define the items that should be shown in the webshop as related products.) Formerly, this tab was activated only on selected accounts.

  9. Product export file now includes the quantities of packaging materials (which can be entered on product card if the respective module has been enabled on your account).

  10. For Estonian customers, a version upgrade notification now displays a link to localized release notes.

  11. Support for TriPOS payment signatures has been added.

Improvements

  1. In product export, product’s net weight and gross weight are now returned in a uniform number format.

  2. When scheduling the tasks on an Assignment, the calendar view that opened when clicking on the “Add”link worked inconsistently. It has been adjusted to work as follows:

    1. If assignment has a location defined, the popup will display location’s calendar.
    2. Otherwise it will display the joint calendar of all user groups designated for repair jobs.
  3. On user group form, the permission check boxes “Add shipping” and “Set tax exemption” are now visible regardless of account’s country. Formerly, these fields were activated only on American and Canadian accounts.

  4. Packing list printout has been improved and unnecessary whitespace between columns removed.

  5. Improvements in report generator:

    1. Column “ID” has been added to all tables.

    2. The error message that appears when trying to group or sort by a calculated column (eg. Sales document → Amount Paid) is now translated.

    3. New columns added: Sales document → Shipment packed by, Sales document → Year and month, Sales document → Payment deadline.

    4. Columns “Year number” and “Month number” in table “Sales document” now allow grouping and sorting.

    5. When grouping the report by a certain value, the value on the subtotal row is now displayed in the same number or date format as the rest of the data.

  6. Actual Reports, purchase document printout: every document row now also includes product pictures.

  7. Danish translations have been updated.

Fixes

  1. Amount in EEK has been removed from purchase document printouts.

  2. Fixed: Inventory Report now respects configuration parameter"users_can_only_see_own_warehouse_stock".

  3. Fixed: when viewing “Unpaid invoices & balance statements” report in a non-default currency, invoice totals were still displayed in default currency.

  4. Fixed: With certain settings, packing list printout had a column alignment issue.

  5. Fixed: obsolete buttons “Google Apps” and “Get Firefox” have been removed from the login form.



ERPLY Classic Back Office version 4.11.10

16 August 2018

Fixes

  1. Fixed: Customer’s web shop password was lost when re-saving customer form.


ERPLY Berlin Back Office version 5.12.6

16 August 2018

Fixes

  1. Fixed: Customer’s web shop password was lost when re-saving customer form.


ERPLY Berlin Back Office version 5.12.5

6 August 2018

Fixes

  1. Items with status “not for sale” could be sold.
  2. Customer’s password was not saved correctly.


Berlin POS version 3.29.1 release notes

24 July 2018

Base version: 3.28.2

New Features

  • Added ability to change payment provider device IP even if a user is not the admin (Cayan)
  • Added Cayan Mini support for iOS (processTransaction, cancelTransaction)
  • Implemented all-in-one and regular receipt printing from Nets-ingenico terminal for Android
  • Added configuration parameter,"touchpos_print_receipt_duplicate_to_secondary_printer" which allows re-print receipt from the secondary printer
  • GDPR – log customer detailed view event from POS
  • Added new transactionTime parameter supplied by Back-Office to providers Nixor and VeriFone Finland

Improvements

  • Remove logo if streamline is printed and POS is offline (Greece fiscal type A)
  • Offline streamline location and size fix – same as online (Greece)
  • Added HTML standard header to all in one receipt (fix font size issue in offline mode)
  • Changed the rules of when a coupon should be redeemed
  • Do not open coupon add view, if coupons are added automatically (conf.param "touchpos_use_customer_coupons_automatically")
  • Added getStockInfo parameter for quick products synchronization to avoid getting 0 stock warning for items with actual stock

Fixes

  • Fix document number retrieve from API before saving the document 
  • Fixed secondary printer displaying issue if a primary printer is payment terminal
  • Fix Greece fiscal type A in offline mode (correct VAT values)


Erply API version 1.25.0, 1.25.1

18 July 2018

New features

  1. Filter "typeID" has been added to API call getPayments.
  2. API call saveProduct now supports adding, modifying and deleting long attributes.

Improvements

  1. Fields "entryMode" and "signatureNotRequired" have been removed from API calls getPayments and savePayment. These fields were related to a payment provider integration that has not been completed and is not in use.

Fixes

  1. Fixed: product pictures added with API call saveProductPicture were not ordered correctly in API output and on back office’s product card.


ERPLY Berlin Back Office version 5.12.4

11 July 2018

Improvements

  1. In Settings → Configuration → Sales document printouts, it is now possible to hide the QR code from sales document printout.
  2. In Settings → Configuration → Receipt printouts, it is now possible to hide the verification code from receipt printout.


ERPLY Classic Back Office version 4.11.9

10 July 2018

Improvements

  1. In Settings → Configuration → Sales document printouts, it is now possible to hide the QR code from sales document printout.
  2. In Settings → Configuration → Receipt printouts, it is now possible to hide the verification code from receipt printout.


ERPLY Berlin Back Office version 5.12.3

27 June 2018

Improvements

  1. In report generator, the field “Total net weight” displayed unexpected values when certain plugins were activated. This field has now been renamed to “Net weight or volume (Intrastat)”, and a new “Total net weight” field has been added which gives weight information as expected.

Fixes

  1. Fixed: QR code overlapped with footer text on invoice PDF printout.

  2. Fixed: Clicking on “More…” → “Send by email” in Purchase Orders module did not work.

  3. Fixed: Option “Send by email in English” for purchase orders sent a PDF where item names were not in English.

  4. Fixed: when viewing “Unpaid invoices & balance statements” report in a non-default currency, invoice totals were still displayed in default currency.


ERPLY Classic Back Office version 4.11.8

27 June 2018

Improvements

  1. Thai translation added.

Fixes

  1. Fixed: QR code overlapped with footer text on invoice PDF printout.
  2. Fixed: when creating a sales order from Inventory → “Pick items to create an order”, customer price list prices did not apply.


ERPLY Classic Back Office version 4.11.7

21 June 2018

Improvements

  1. French translations updated.


ERPLY Classic Back Office version 4.11.6

20 June 2018

Improvements

  1. Finnish translations updated.


ERPLY Berlin Back Office version 5.12.2

19 June 2018

Improvements

  1. Finnish translations updated.


ERPLY Berlin Back Office version 5.12.1

18 June 2018

Fixes

  1. Fixed: Links to documents and quotes on Project form did not open.
  2. Fixed: in Finnish, product’s number of stock days was not displayed on product card.


ERPLY Berlin Back Office version 5.12.0

13 June 2018

New Features

  1. Compliance with General Data Protection Regulation can now be activated on demand on non-EU accounts, too — with configuration parameter "gdpr_features_enabled" = 1.

  2. A setting has been added: Settings → Configuration → “Inventory and purchase” → “”Show in webshop” is checked by default for new products and product groups”. To have all new products created with “Show in webshop” turned off by default, uncheck this box.

  3. “Anonymous printout” option has been added to sales documents. If a customer wants to be identified for the transaction, but does not want the printout to contain their personal information, select “Download anonymous printout” or “Send anonymous printout by email” from the “More…” dropdown or “Print / Send” dialog window.

  4. A “verification code” has been added to invoice and receipt printouts. With this code, we will be able to verify if a particular receipt or an invoice originates from Erply, and whether the transaction details are correct — or has the printout been forged or modified (eg. to commit tax fraud).

    On invoice printouts, the verification code also appears as a QR code.

  5. A customer’s web shop password can now be deleted. (Click on the “Delete” link next to the field and re-save the customer.)

  6. A user’s PIN can now be deleted. (Click on the “Delete” link next to the field and re-save the user.)

  7. Links “Select all” and “Select none” have been added to user form, next to the “Locations” heading, to check or uncheck all locations at once.

  8. In the Users list, if the list of locations (to which the user has access) is longer than 15, just a total number of locations will be displayed, instead of the name of each one. (Eg. “20/25”, meaning that user has access to 20 locations out of 25 total.)

  9. Report “Distribute Goods to Selected Location” in Reports → Inventory:

    • Now respects all filters (product group, category, brand, supplier, priority group; product; product extra fields 1-4);
    • Adds selected items to an existing open Transfer Order if one exists (ie., no longer creates a new Transfer Order each time);
    • In its suggestions ( “Total required” and “To be transfered”), it takes into account if a purchase order or transfer order has already been created.
  10. The product card of a matrix variation now displays what is the size and color of this variation, and provides a link to the parent product.

Improvements

  1. On non-EU accounts, person names are now displayed again in the following reports:

    • Reports → Sales
    • Reports → Cost of Goods Sold
    • Reports → Invoices and payments
  2. Greek translations updated.

  3. One French translation updated.

  4. In Purchase → Purchase orders, unnecessary column “Deadline” has been replaced with “Delivery date”.

  5. On Stock Replenishment Report, in the “Packages to order” drop-down, packages are now listed in order of creation.

  6. Setting “In Berlin POS, plugins are mandatory” has been added to Settings → Configuration → POS. This is a pre-existing setting that can also be turned on or off from Berlin POS user interface. The check box in back office has been provided as a backup, for the case when POS cannot even be opened due to a broken plugin.

Fixes

  1. Fixed: when fetching an Actual Reports sales document printout in a different language, product unit names were not translated.

  2. Fixed: on sales documents that use retail calculation algorithm, invoice lines appeared shifted (an extra field appeared on some lines).

  3. Fixed: searching for a purchase order by an alphanumeric order tracking number, or searching for a purchase invoice by an alphanumeric invoice number returned irrelevant search results.



Back Office versioon 4.11.0 - 4.11.5

11 June 2018

11. juuni 2018

Uued võimalused

  1. GDPRi vastavust saab nüüd soovi korral seadistada ka EL-i välistele kontodele, parameetriga "gdpr_features_enabled" = 1.
  2. Lisatud uus seadistus: Seaded → Üldseadistused → Ladu ja ost → “”Näita e-poes” linnuke on uutele toodetele ja tootegruppidele vaikimisi sisse lülitatud”. Kui soovite, et uutel toodetel ei oleks linnukest “Näita e-poes” automaatselt peal, võtke sellelt parameetrilt linnuke maha.
  3. Müügidokumentidele on lisatud uus võimalus “Anonüümne väljatrükk”, juhuks kui klient soovib, et teda tehingu käigus identifitseeritaks, kuid ei soovi, et väljatrükk sisaldaks isiklikke andmeid. Valiku leiab “Veel” → “Anonüümne väljatrükk (PDF)” või “Saada anonüümne väljatrükk e-postiga”.
  4. Müügidokumentide väljatrükile on lisatud “kinnituskood”, mille abil on meil võimalik tuvastada, kas antud dokument pärineb Erplyst ning kas tehingu andmed on õiged. Või on väljatrükki keegi võltsinud või muutnud (nt maksupettuse tarbeks). Müügidokumentide väljatrükil kuvatakse seda lisaks ka QR koodina.
  5. Kohandatud väljatrükki (Actual Reports) lisandus uus väli, mis võimaldab müügidokumentide väljatrükkidel kuvada iga toote laoseisu. (Väljade nimetused on "amountInStock", "amountReserved", ning "amountAvailable".)

 

Täiendused

  1. EL-i välistel kontodel kuvatakse nüüd taas eraklientide nimesid järgnevates aruannetes:
    • Aruanded → Müük-müügikäive
    • Aruanded → Müük-laokäive
    • Aruanded → Kassa ja laekumised
  2. Prantsuse tõlge täiendatud.
  3. Laovarude täiendamise aruandes kuvatakse nüüd “tellitav kogus pakendites” rippmenüüd loomise järjekorras.
  4. Aruandegeneraatoris kuvas “Netohind kokku” teatud pluginate koosmõjul valet infot. Väli on nüüd ümber nimetatud “Netokaal või maht (Intrastat)” ning lisatud on uus väli nimetusega “Netohind kokku”, mis annab ootuspärase kaaluinfo.
  5. Sularahaarveid saab nüüd alla laadida PDF-na.
  6. Müügidokumentide alt on eemaldatud valik “Saada e-mailiga”. Enam ei ole võimalik saata müügidokumente HTML-na. Selle asemel soovitame saata PDF-na, kasutades valikut “Saada e-mailiga (PDF)”.
  7. Parandatud: ettevõtte aadress kuvatakse arvete jaluses nüüd mitmel real, et tagada parem asetus PDF-del.

 

Parandused

  1. Parandatud: müügitehing, kus komplekttootele tehti allahindlust, tekkis Erplysse valede andmetega (Müügidokumentide summad kuvati valesti, kui aruande filtris oli määratud “Näita komplekttoodete müüki: komponentide kaupa eraldi”).
  2. Parandatud: müügidokumendi kohandatud väljatrükil (Actual Reports) olid teistes keeltes trükkides toodete ühikute nimetused tõlkimata.
  3. Parandatud: frantsiisikontol kuvati veateadet, kui kasutaja, kellel polnud õigust näha ostuhinda, proovis kinnitada ostuarve.


ERPLY Classic Back Office version 4.11.0 - 4.11.5

11 June 2018

New features

  1. Compliance with General Data Protection Regulation can now be activated on demand on non-EU accounts, too — with configuration parameter "gdpr_features_enabled" = 1.

  2. A setting has been added: Settings → Configuration → Inventory and purchase → “”Show in webshop” is checked by default for new products and product groups”. To have all new products created with “Show in webshop” turned off by default, uncheck this box.

  3. “Anonymous printout” option has been added to sales documents. If a customer wants to be identified for the transaction, but does not want the printout to contain their personal information, select “More…” → “Anonymous printout (PDF)” or “Send anonymous printout by email”.

  4. A “verification code” has been added to invoice and receipt printouts. With this code, we will be able to verify if a particular receipt or an invoice originates from Erply, and whether the transaction details are correct — or has the printout been forged or modified (eg. to commit tax fraud).

    On invoice printouts, the verification code also appears as a QR code.

  5. On Actual Reports sales document printouts, a new field is available: each product’s quantity in stock. (Field names are "amountInStock", "amountReserved", and "amountAvailable".)

Improvements

  1. On non-EU accounts, person names are now displayed again in the following reports:

    • Reports → Sales
    • Reports → Cost of Goods Sold
    • Reports → Invoices and payments
  2. One French translation fixed.

  3. On Stock Replenishment Report, in the “Packages to order” drop-down, packages are now listed in order of creation.

  4. A validation on price list form, related to configuration parameter "do_not_allow_to_add_flyer_items_to_store_pricelist", has been improved.

  5. In report generator, the field “Total net weight” displayed unexpected values when certain plugins were activated. This field has now been renamed to “Net weight or volume (Intrastat)” and a new “Total net weight” field has been added which gives weight information as expected.

  6. Receipts can now be downloaded as PDFs.

  7. For receipts and invoices, the option “Send by email” has been removed. This option allowed to send the document as an HTML attachment. We recommend to send documents as PDFs instead, by selecting “Send by email (PDF)”.

  8. Fixed: company address in invoice printout footer is now always displayed on multiple lines, to avoid layout issues in PDFs.

Fixes

  1. Fixed: if a sold bundle was discounted, the sales document was created with incorrect data. (In reports, when selecting the option “Display sold bundles: by components separately”, sales report totals were incorrect.)

  2. Fixed: when fetching an Actual Reports sales document printout in a different language, product unit names were not translated.

  3. Fixed: an error occurred if user attempted to confirm a purchase invoice on a franchise account, without having the rights to see product cost.



Erply API version 1.24.0

7 June 2018

New features

  1. Support for Klarna payment integration has been added: field "klarnaPaymentID" has been added to API calls getPayments and savePayment. To enable this feature on your account, please contact customer support.

  2. Search field "referenceNumber" has been added to API calls getSalesDocuments and getPurchaseDocuments.

  3. Field "epsiDownloadURLs" has been added to API calls verifyUser, switchUser and changePassword. It contains EPSI installer URLs for each operating system.

  4. The following fields (specific to wholesale of alcoholic beverages) have been added to API calls getProducts and saveProduct. To have these extra product fields on your account, please contact customer support.

    • registryNumber
    • alcoholPercentage
    • batches
    • exciseDeclaration
    • exciseFermentedProductUnder6
    • exciseWineOver6
    • exciseFermentedProductOver6
    • exciseIntermediateProduct
    • exciseOtherAlcohol
    • excisePackaging
  5. Field "packagingType", related to packaging report, has been added to API calls getProducts and saveProduct.

  6. API now supports back office configuration checkbox “”Show in webshop” is checked by default for new products and product groups”. (This checkbox will be added in Classic back office 4.11 and Berlin back office 5.12.)

Improvements

  1. A validation in API calls addProductToPriceList and savePriceList, related to configuration parameter "do_not_allow_to_add_flyer_items_to_store_pricelist", has been improved.

  2. API call getFranchiseSalesDocuments can now detect cross-franchise returns and will return appropriately reduced quantities when queried with "nonReturnedItemsOnly" = 1.

Fixes

  1. Fixed: API call getProductCostForSpecificAmount returned an incorrect response.


ERPLY Berlin Back Office version 5.11.1

31 May 2018

Fixes

  1. Fixed: API call “getSalesReport” returned an error.
  2. Fixed: On receipts printed through EPSI, receipt lines had a too large font size. (Receipt size fix also requires Berlin POS version 3.28.7 or newer.)


Back Office versioon 4.10.0

21 May 2018

21. mai 2018

Uued võimalused

  1. Lisatud on uued võimalused kontrollimaks töötajate ligipääsu kliendiandmetele. Võttes arvesse isikuandmete kaitse üldmäärust (GDPR), on tähtis, et töötajad oleksid koolitatud õiguspäraselt isikuandmeid töötlema (Oleme ka kirjutanud blogipostituse).

Seaded → Üldseadistused all on nüüd võimalik keelata volitamata töötajatele ligipääs kliendiandmetele. Töötajate mooduli kaudu saab töötajaid ükshaaval autoriseerida. Selleks on töötaja kaardile lisatud kaks uut nuppu:

    1. Esimene näitab töötaja kinnitust, et ta on teadlik määrusest ning klientide õigusest ning teab kuidas kaitsta isikuandmeid.
    2. Teine näitab, et juht on andnud töötajale ligipääsu klientide andmetele.

Vorm näitab ära, millal töötaja selle kinnitas ning kes ja millal on töötajale ligipääsu andnud.
Tegemist on lisamooduliga. Mooduli aktiveerimiseks võtke ühendust kasutajatoega.

  1. Seaded → Üldseadistused alt saab nüüd valida, kuidas kuvatakse töötaja nimi  a) müügidokumentide väljatrükil, ning b) sularahaarvete väljatrükil:
    1. Ainult ID;
    2. Ainult eesnimi;
    3. Eesnimi, koos perenime initsiaaliga; või
    4. Täisnimi.
  2. “Seaded” → “Üldseadistused” → “Müügidokumentide väljatrükid” alt saab nüüd seadistada, millist kliendiinfot kuvatakse tšeki väljatrükil (Väljatrükki saab seadistada eraldi ettevõtetele ja eraklientidele):
    1. Kliendi ID
    2. Kliendikaardi kood
    3. Kliendi nimi
    4. Kliendi aadress
  3. Püsikliendi punkte saab nüüd trükkida ka tšekkidele. Seadistusvõimalus lisatud “Seaded→ “Üldseadistused” → “Müügidokumentide väljatrükid” all.
  4. Kliente saab otsida kliendi ID järgi, väli “Kliendi ID” on lisatud kliendikaardile.
  5. Töötajaid saab otsida ID järgi, väli “Töötaja ID” on lisatud töötajakaardile.
  6. Kliendi e-poe parooli saab nüüd kustutada (Kliendikaardil klikake lahtri kõrval asuval “Kustuta” lingil ning seejärel salvestada kliendikaart).
  7. Kasutaja PIN-koodi saab nüüd kustutada (Kasutajakaardil klikake lahtri kõrval asuval “Kustuta” lingil ning seejärel salvestage kasutajakaart).

Täiendused

  1. Arvete saatmisega seotud tegevused ning e-postiga saatmise logi (nii müügi- kui ostudokumentidel) ei kuva enam välja saatja ning kirja saaja täielikke e-maili aadresse, vaid on osaliselt peidetud, nt “test@example.com” on muudetud “tes…@exa…”
  2. Et eraklientide isikuandmeid liigselt mitte avaldada, ei kuvata järgmistes aruannetes enam klientide nimesid. Selle asemel kuvatakse kliendi ID ja link kliendikaardile. Ettevõtete nimed kuvatakse välja nii nagu varem.  
    • Aruanded → Müük – müügikäive
    • Aruanded → Müük – laokäive
    • Aruanded → Kassa ja laekumised
  3. Et eraklientide isikuandmeid liigselt mitte avaldada, ei kuvata järgmistes aruannetes enam klientide nimesid. Selle asemel kuvatakse kliendi ID ja link kliendikaardile.
    • Aruanded → Kupongid, kinkekaardid → Näita aruannet
    • Aruanded → Kupongid, kinkekaardid→ Aktiivsed kinkekaardid
    • Aruanded → Müügikampaaniad
    • Aruanded → Tegevused
  4. Liidestades Verifone Finlandi või Nixpay (Atos Worldline terminal) makseterminali Erplyga, kuvatakse veateade, kui kontol pole aktiveeritud moodulit “Transaction Time of a Payment”. Aktiveerimiseks võtke ühendust kasutajatoega.

Parandused

  1. Kui kontol on kasutusel eraldiseisev klienditeenus, ei kuvata enam “Süsteemi uuendus” teadet, kui klienditeenuselt ei saada vastust või vastuse ootamine võtab liiga kaua aega. Vastust oodatakse senise 5 sekundi asemel nüüd 10 sekundit.


Erply API version 1.23.0

21 May 2018

New features

  1. New API call recordGDPRConfirmation has been added.

  2. Support for the employee authorization process, introduced in Classic back office 4.10 and Berlin back office 5.11, has been added. If the restrictions have been enabled from back office and user has not been given access yet, API will prevent user from accessing customer information.

  3. New API call logProcessingOfCustomerData has been added. Use this call to log customer processing activities that have taken place outside of Erply if it is not possible to keep a log elsewhere.

Fixes

  1. Fixed: when editing an existing product, API call saveProduct will no longer reset the product’s tax rate to the default value if no tax rate is provided.

  2. Fixed: applying promotions “Buy 3 pcs of Product X for $10” to a sale was a very slow process.

  3. When using a standalone customer registry, a timeout or no response from the registry no longer causes a fatal error (error 1000). Timeout has been increased from 5 to 10 seconds.



ERPLY Berlin Back Office version 5.11.0

21 May 2018

New features

  1. New tools for controlling employees’ access to customer data have been added. Considering the General Data Protection Regulation (GDPR), it is important that employees are trained to handle personal data properly. (We have also written about GDPR on Erply blog.)

    In Settings → Configuration, it is now possible to disable unauthorized employees’ access to customer information. Employees can be authorized one by one from the Employees module. Two new buttons have been added to employee form:

    1. One to indicate employee’s confirmation that they are familiar with the regulation and customers’ rights, and know how to protect personal information.
    2. Another one to indicate that a manager has allowed the employee to access customer data.

    The form also shows when employee gave their confirmation, and who and when gave them the access.

    This feature is an extra module. If it has not been activated on your account yet, please contact customer support.

  2. In Settings → Configuration, it is now possible to select whether employee name on a) sales document printouts and b) receipt printouts should be displayed as:

    1. ID only;
    2. first name only;
    3. first name, with last name initial; or
    4. full name.
  3. In Settings → Configuration → Receipt printouts, it is now possible to configure what information about a customer should be displayed on a receipt printout. (The printout can be configured separately for companies and for persons.)

    1. Customer ID
    2. Customer card code
    3. Customer name
    4. Customer address
  4. Customer’s amount of reward points can now be printed on receipts. This option has been added to Settings → Configuration → Receipt printouts.

  5. Customers can be looked up by ID, and field “Customer ID” has been added to customer card.

  6. Employees can be looked up by ID, and field “Employee ID” has been added to employee form.

Improvements

  1. To not expose personal information unnecessarily, the following reports no longer display the name of a customer if that customer is a person. (Customer ID is shown instead, and a link to customer card is provided. Names of companies are still displayed, though.)

    • Reports → Sales
    • Reports → Cost of Goods Sold
    • Reports → Invoices and Payments
  2. To not expose personal information unnecessarily, the following reports no longer show the names of any customers. (Customer ID is shown instead, and there is also a link to customer card.)

    • Reports → Coupons, gift cards → Show report
    • Reports → Coupons, gift cards → Active Gift cards
    • Reports → Sales promotions
    • Reports → Tasks


ERPLY Classic Back Office version 4.10.0

21 May 2018

New features

  1. Fields “Deposit fee” and “Fee quantity” have been added to product card. These fields allow to associate a product with a deposit fee (recycle fee).

    Deposit fees, or recycle fees, are a legal requirement in many countries. Whenever certain products are sold, the merchant needs to collect a deposit.

    In Erply, define the deposit fee as a separate product. Set it VAT-free if needed. Then, look up a product that needs to be sold together with a deposit fee, click on the “Deposit fee” field on product card and select the fee.

    Field “Fee quantity” may be usually left empty. It is needed only if the item you are selling is a larger package — for example a six-pack of soda (where you need to collect 6 deposit fees per each six-pack).

    When you add a product with a deposit fee to the sale, the deposit fee is automatically added, too, as a separate line. Deposit fees are supported:

    • in Berlin POS;
    • on Invoices, Sales Orders and Quotes in back office.
  2. New tools for controlling employees’ access to customer data have been added. Considering the General Data Protection Regulation (GDPR), it is important that employees are trained to handle personal data properly. (We have also written about GDPR on Erply blog.)

    In Settings → Configuration, it is now possible to disable unauthorized employees’ access to customer information. Employees can be authorized one by one from the Employees module. Two new buttons have been added to employee form:

    1. One to indicate employee’s confirmation that they are familiar with the regulation and customers’ rights, and know how to protect personal information.
    2. Another one to indicate that a manager has allowed the employee to access customer data.

    The form also shows when employee gave their confirmation, and who and when gave them the access.

    This feature is an extra module. If it has not been activated on your account yet, please contact customer support.

  3. In Settings → Configuration, it is now possible to select whether employee name on a) sales document printouts and b) receipt printouts should be displayed as:

    1. ID only;
    2. first name only;
    3. first name, with last name initial; or
    4. full name.
  4. In Settings → Configuration → Receipt printouts, it is now possible to configure what information about a customer should be displayed on a receipt printout. (The printout can be configured separately for companies and for persons.)

    1. Customer ID
    2. Customer card code
    3. Customer name
    4. Customer address
  5. Customer’s amount of reward points can now be printed on receipts. This option has been added to Settings → Configuration → Receipt printouts.

  6. Customers can be looked up by ID, and field “Customer ID” has been added to customer card.

  7. Employees can be looked up by ID, and field “Employee ID” has been added to employee form.

  8. A customer’s web shop password can now be deleted. (Click on the “Delete” link next to the field and re-save the customer.)

  9. A user’s PIN can now be deleted. (Click on the “Delete” link next to the field and re-save the user.)

Improvements

  1. Tasks titled “Invoice … sent by e-mail” (which Erply creates automatically if you send a document by email) and the “E-mail log” on sales and purchase documents will no longer contain sender’s and recipient’s full addresses. Email addresses in these records are now partially masked with asterisks: an address "test@example.com" becomes "tes...@exa...", for example.

  2. To not expose personal information unnecessarily, the following reports no longer display the name of a customer if that customer is a person. (Customer ID is shown instead, and a link to customer card is provided. Names of companies are still displayed, though.)

    • Reports → Sales
    • Reports → Cost of Goods Sold
    • Reports → Invoices and Payments
  3. To not expose personal information unnecessarily, the following reports no longer show the names of any customers. (Customer ID is shown instead, and there is also a link to customer card.)

    • Reports → Coupons, gift cards → Show report
    • Reports → Coupons, gift cards → Active Gift cards
    • Reports → Sales promotions
    • Reports → Tasks
  4. When configuring a register to use Verifone Finland or Nixpay (with Atos Worldline terminal) payments, an error message will be displayed if extra module “Transaction Time of a Payment” has not been installed on your account. This module is required for Verifone Finland and Nixpay payments. When needed, please contact customer support to activate this module.

Fixes

  1. When using a standalone customer registry, a timeout or no response from the registry no longer causes a “System Update” page to be displayed. Timeout has been increased from 5 to 10 seconds.


Erply API version 1.22.4

24 April 2018

New features

  1. API call savePayment now accepts new input parameter "transactionTime" for Verifone Finland and Nixpay (Nixor) payments.

    This extra field is needed for Berlin POS. To make this field available, extra module “Transaction Time of a Payment” needs to be installed to your account. Please contact customer support for that. Without that extra module, these two payment integrations cannot be used.

    Classic back office (starting with version 4.10) and Berlin back office (starting with version 5.10) will warn if you attempt to configure a register to use Verifone Finland or Nixpay (Atos Worldline) payments, and this module has not been installed yet.

Fixes

  1. Fixed: in a bulk request, it was not possible to make queries in different languages (eg. to retrieve product names in English and product groups in German). This caused an issue with weighted products on Greek accounts.


ERPLY Berlin Back Office version 5.10.0 - 5.10.2

24 April 2018

New features

  1. To improve delivery, e-mails sent from Erply will now have “noreply@erplyinfo.com” as the sender’s address.

    Sending e-mail from our own domain name allows us to properly sign the messages and prove that the e-mail has originated from Erply. Many receiving mail servers take note if the “From” address does not match the originating server, and assign the message a higher spam score, or discard it entirely.

    Therefore, this change was necessary to make sure that we follow the best practices and established standards.

    Naturally, the receiver needs to know who has sent the message, and must be able to reply to it. We will put your company name on the “From:” line, and we will also set a “Reply-To” header with your actual e-mail address.

    Thus, the e-mails are going to look like this:

    From: Sample Company <noreply@erplyinfo.com>
    Reply-To: Sample Company <info@samplecompany.com>
    
  2. Deposit Fee support has been added.

    Fields “Deposit fee” and “Fee quantity” have been added to product card. These fields allow to associate a product with a deposit fee (recycle fee).

    Deposit fees, or recycle fees, are a legal requirement in many countries. Whenever certain products are sold, the merchant needs to collect a deposit.

    In Erply, define the deposit fee (recycle fee) as a separate product. Set it VAT-free if needed. Then, look up a product that needs to be sold together with a deposit fee, click on the “Deposit fee” field on product card and select the fee.

    Field “Fee quantity” may be usually left empty. It is needed only if you sell an item in a larger package, and this package is defined as a separate product in your product catalog. A typical example would be a six-pack of soda. For each 6-pack, you need to collect 6 deposit fees; therefore, enter “6” into the “Fee quantity” field.

    When you add a product with a deposit fee to the sale (or scan the item), the deposit fee is automatically added to the document, too — as a separate line. Deposit fees are supported:

    • In Berlin POS;
    • on Invoices, Sales Orders and Quotes in back office.


    When you change the product’s quantity, the fee’s quantity automatically updates. When you remove the product, the fee gets removed, too.

    Note that deposit fees are not automatically added when creating a purchase document, an Inventory Registration, an Inventory Write-Off or an Inventory Transfer.

Improvements

  1. When a sales document, purchase document, balance statement or payment reminder is sent by e-mail, this is recorded in the system as a “task”. These tasks can be seen in Calendar → Tasks, if you have the respective module enabled on your account.

    On sales documents, the sending history can additionally be seen by clicking on the “…” button and selecting “E-mail log”.

    To avoid storing unnecessary personal information in Erply, these records will no longer contain full sender’s and recipient’s addresses. The addresses will be partially masked with asterisks: an address "test@example.com" becomes "tes...@exa...", for example.

  2. When configuring a register to use Verifone Finland or Nixpay (with Atos Worldline terminal) payments, an error message will be displayed if extra module “Transaction Time of a Payment” has not been installed on your account. This module is required for Verifone Finland and Nixpay payments. When needed, please contact customer support to activate this module.

  3. User’s password can now be changed from the Users table and from User form. Formerly, the link for changing a password was only located in the Employees table.

  4. A few Lithuanian translations have been updated.

  5. On a receipt printout, blocks of card payment information are now identifiable by HTML classes. (This is needed for Berlin POS.)

Fixes

  1. Fixed: in product catalog, clicking twice on the “M+” link (to see a matrix product’s variations) displayed an error page.
  2. Fixed: on Matrix Dimension form (in PIM → Matrix Dimensions), reordering the dimension values (by clicking on up and down arrows) sometimes did not work.
  3. Fixed: in certain cases, the first line in an SEB bank payment import file was handled incorrectly, which could cause the same payment to be imported again later as a duplicate.
  4. Fixed: on a franchise account, in the “Settings → Log of deleted items” module, clicking on the “Time” column to sort records by time produced an error.
  5. Fixed: when printing labels for matrix variations from a price list, the labels displayed an incorrect price.
  6. Fixed: in the “Inventory” table, columns “Price” and “Price with VAT” were truncated on a smaller screen, and part of the price was invisible.
  7. Fixed: in a report generator report with two-level grouping, some subtotal lines were missing.
  8. Fixed: in report generator, the “Warehouse value” column for purchase invoice rows was empty.


Erply API version 1.22.3

19 April 2018

Bug fixes

  1. Fixed: API calculateShoppingCart calculated a “$ off entire invoice” promotion discount incorrectly when customer purchased a gift card.


Erply API version 1.22.2

17 April 2018

Bug fixes

  1. Fixed: if one API call in a bulk request fails with error code 1005, 1006 or 1009, the remaining calls will now be executed, too. Formerly, API terminated the bulk request, returned a response and ignored all the remaining calls.

  2. Fixed: Promotion “Get % off all items” with the additional check box “Except lines to which a manual discount or any other price list or promotion discount has already applied” was incorrectly regarded as successful, even when all items in the shopping cart already had a prior discount, and thus the promotion did not actually discount any items. As a result, a coupon was unnecessarily redeemed.



Erply API version 1.21.9

17 April 2018
  1. Fixed: if one API call in a bulk request fails with error code 1005, 1006 or 1009, the remaining calls will now be executed, too. Formerly, API terminated the bulk request, returned a response and ignored all the remaining calls.


Back Office versioon 4.9.0

12 April 2018

12. aprill 2018

Uued võimalused

  1.  Et tõhustada e-kirja kohaletoimetamist, saadetakse Erplyst e-kirjad nüüdsest välja saatja aadressiga noreply@erplyinfo.com. E-kirjade saatmine meie enda domeenilt võimaldab meil sõnumeid korrektselt allkirjastada ja tõendada, et saadetud kiri pärineb Erply-st. Paljud vastuvõtvad e-posti serverid jälgivad, kas saatja aadress vastab päritoluserverile ning erinevuse korral määravad sõnumile suurema rämpsposti skoori või loobuvad vastuvõtmisest täielikult. Selleks, et kirja vastuvõtja siiski näeks, kellelt kiri on tulnud, ja saaks sellele ka vastata, lisame “From” aadressireale saatja ettevõtte nime ning lisame ka saatja e-posti aadressi “Reply-To” reale. Erplyst väljasaadetavad e-kirjad hakkavad välja nägema nii:
    From: Sample Company <noreply@erplyinfo.com>
    Reply-To: Sample Company <info@samplecompany.com>
    
  2. Lisatud on uus kampaanialiik “Ühiku erihind”. Seda tüüpi müügikampaania korral saab klient teatud tooted soodushinnaga, kui ta ostab vähemalt teatud koguse. Kampaania tuleks sel juhul luua järgmiselt:1. Kampaaniakirjelduse vasakul küljel (“Klient peab”) tuleb määrata toode (või tooterühm või -kategooria) ja minimaalne kogus, mida klient peab ostma, et kampaania rakenduks;
    2. Parempoolsel küljel (“Klient saab”) tuleb määrata uus ühikuhind, mis rakendub kampaaniatingimuste täitmisel. Välja pealkiri on “Või valitud esemed ja kõik järgnevad analoogsed tooted ühikuhinnaga…”. Kampaaniale saab määrata ka piirangu: maksimaalselt mitu soodustusega toodet klient saab osta.
  3. Kampaaniatele on lisatud valik “Lunastamise piirang”.Lunastamise piirang võimaldab määrata, mitu korda kampaania ühe müügi korral rakendub. Või, kui tegemist on kupongi kampaaniaga, siis võib klient lunastada müügil ainult teatud arvu kuponge. Näiteks kampaania korral “Osta 2 pirukat ja saad õunalt 50% alla”. Piiranguväljale märgitud 3 tähendab seda, et olenemata sellest, millises koguses klient ostab, saavad nad ainult maksimaalselt 3 soodushinnaga õuna (Ja sellisel juhul on neil tarvis osta 6 pirukat).Lunastamispiiri ei tohiks segi ajada “maksimaalse allahinnatud toodete arvuga”. Mõned kampaaniatüübid võimaldavad mõlemat võimalust; siin tuleks hoolikalt läbi mõelda, mida täpselt tarvis on. Väljund asub vormi lõpus ja on pealkirjaga “Määra, mitu korda võib ostule maksimaalselt rakenduda muud liiki kampaania: “.
  4. Müügikampaania vorm on ümber kujundatud. 
    Lisatud on informatiivne väli “Kuidas kampaania ostule rakendub”, mis annab kiirülevaate, kas tegemist on automaatse, kupongi või
    käsitsi rakendatava kampaaniaga; ning selgitab, kui mitu korda kampaania rakendub (ainult üks kord / nii palju kordi kui võimalik / jne). Igal kampaaniatüübil on erinevad reeglid ja see väli peaks kampaania algoritmi muutma läbipaistvamaks.

Täiendused

  1. Dialoogiaken “E-kirja koostamine” hoiatab, kui saatja aadress on väär või kui on määratud mitu saatjat.
  2. Lisatud on tugi API käsklusele addPromotionCountsToInvoice (kui haldurist kustutatakse müügidokument, kustub ka selle külge salvestatud lisainfo rakendunud kampaaniate kohta).
  3. Versiooniuuenduses 4.8.5 nimetatud parameetrite nimetused on täiendatud vastavalt "customer_registry_group_cache_time" ning "customer_registry_customer_cache_time".

Parandused

  1. Parandatud: aruandegeneraatoris kahetasandilise grupeerimise korral mõningad vahesumma read puudusid.
  2. Parandatud: dialoogiaken “E-kirja koostamine” ei arvestanud seadistust “Saada arveid: Kliendi meiliaadressile / Maksja meiliaadressile”.
  3. Kampaania vormil kuvatakse nüüd rippmenüüs “Kampaania rakendub ainult nendele kliendigruppidele” kliendigruppe hierarhiliselt. Kampaaniate piiramine regiooniti või kliendigrupiti vajab lisamooduli seadistust kasutajatoe poolt.

 



ERPLY Classic Back Office version 4.9.0

12 April 2018

New features

  1. To improve e-mail delivery, e-mails sent from Erply back office will now have “noreply@erplyinfo.com” as the sender’s address.

    Sending e-mail from our own domain name allows us to properly sign the messages and prove that the e-mail has originated from Erply. Many receiving mail servers take note if the “From” address does not match the originating server, and assign the message a higher spam score, or discard it entirely.

    We will still put sender’s company name on the “From:” line, and we will also set a “Reply-To” header with your actual e-mail address. This should ensure that the receiver recognizes who sent the message, and can reply to it.

    Thus, the e-mails are going to look like this:

    From: Sample Company <noreply@erplyinfo.com>
    Reply-To: Sample Company <info@samplecompany.com>
    
  2. New promotion type “Special Unit Price” has been added.

    In this type of promotion, customer gets a discounted price for specific products if they buy at least a certain quantity.

    “Special Unit Price” promotion must be set up as follows:

    1. On the left side (“Customer must”), specify the products (or product group, or category) and the minimum quantity that the customer must buy;
    2. On the right side (“Customer will”), specify the new unit price. The field is titled: “Or, get these items, and each subsequent matching item, for a special unit price of …”

    The promotion may also be set up with a limit: maximum number of discounted items per sale.

  3. “Redemption Limit” option has been added to promotions.

    A Redemption Limit means that a promotion may not apply to one sale more than the specified number of times. Or — if it is a coupon promotion — that the customer may only redeem a specific number of coupons per sale.

    Consider a promotion “Buy 2 pies and get an apple 50% off”. A Redemption Limit of 3 means that regardless of what quantity the customer purchases, they will only get 3 discounted apples at most. (And to get those, they need to buy 6 pies.)

    Redemption Limit should not be confused with “maximum number of discounted items”. Some promotion types allow both options; consider carefully which one you might need.

    The field is located at the end of the form, and is titled “Limit how many times a promotion of any other type can apply to a sale (Redemption limit)”.

  4. Promotion form has been rearranged.

    An informative field “How the promotion applies to a sale” has also been added. It reminds whether the promotion is an automatic, coupon or manual promotion; and explains how many times the promotion is going to apply (only once / as many times as possible / etc.) Each promotion type has different rules, and this field should make promotion algorithm more transparent.

Improvements

  1. “Send by e-mail” dialog now warns if the sender’s address is invalid, or if multiple senders have been specified.
  2. Support for API call addPromotionCountsToInvoice has been added. (When a sales document is deleted from back office, its promotion counts are deleted, too.)
  3. Names of the two parameters introduced in 4.8.5 have been updated to "customer_registry_group_cache_time" and "customer_registry_customer_cache_time", respectively.

Bug fixes

  1. Fixed: in a report generator report with two-level grouping, some subtotal lines were missing.
  2. Fixed: “Send by e-mail” dialog did not respect the setting “Send invoices to: Customer’s e-mail / Recipient of goods’ e-mail”.
  3. On promotion form, the “Promotion only applies to these customer groups” drop-down now shows customer groups as a hierarchical tree.


Erply API version 1.22.0

10 April 2018

New features

  1. API call calculateShoppingCart now supports new promotion type “Special Unit Price”. In this type of promotion, shopper gets a special price for specific products if they buy at least a certain quantity.

    The promotion may also be set up with a limit: maximum number of discounted items per sale.

    To set up this new type of promotion, Classic back office is required — version 4.9 or newer. Alternatively, the promotion can be created over API, with the saveCampaign call. (New input fields"specialUnitPrice" and "maxItemsWithSpecialUnitPrice" have been added.)

  2. API call calculateShoppingCart now supports “Redemption Limit”. This is a way to specify that a promotion may not apply to one sale more than the specified number of times.

    A Redemption Limit of 3, for a promotion “Buy 2 pies and get an apple 50% off”, means that regardless of the quantities the customer purchases, they will only get 3 discounted apples at most. (And to get those, they need to buy 6 pies.)

    Redemption Limit should not be confused with “maximum number of discounted items”. Consider carefully which one you might need.

    To set up promotions with Redemption Limits, Classic back office is required — version 4.9 or newer. Alternatively, it can be set over API, with the saveCampaign call. (New input field "redemptionLimit"has been added.)

  3. Algorithm for the following two promotion types:

    • Buy one product and get % or $ off another product (Buy One Get One)
    • Get N pcs. of a product for a fixed total

    has been changed. As coupon promotions, they will now apply only once per scanned coupon. And when using them manually, cashier must specify how many times they want to apply it.

    If you set up a coupon promotion “Free apple with every pie”, and customer picks three pies and three apples, they will now need to have three coupons as well. Formerly, scanning just one coupon would have given all 3 apples free of charge.

  4. Support for a standalone coupon microservice has been added.

  5. API call addPromotionCountsToInvoice has been added. This is meant for Berlin POS, for reporting how many times each promotion applied to a sale.

    1. This data is only used for custom integrations at the moment. This data cannot be managed from back office, or retrieved over API.
    2. This feature needs to be installed to an account as an extra module, “Promotion Count on Invoice”.
  6. API call calculateRewardPoints has been added. This is a custom integration hook for Berlin POS.

Improvements

  1. Filters "searchEmail" and "searchMobile" have been added to API call getCustomers.
  2. Field "timeZone" (store time zone) has been added to API calls getWarehouses and saveWarehouse.
  3. Field "promotionReasonCodeID" has been added to API call getAppliedPromotionRecords.
  4. Field "warehouseValue" in API call getSalesDocuments, on each invoice row, which previously was undocumented, has now been documented. This field returns the unit cost of sold item. To retrieve that field, use input flag "getCOGS" = 1.
    1. Please note that the unit cost is returned in invoice currency. To get the value in account’s main currency, multiply it by the field "currencyRate".
  5. Names of the two parameters introduced in 1.21.6 have been updated to "customer_registry_group_cache_time" and "customer_registry_customer_cache_time", respectively.

Bug fixes

  1. Fixed: input parameter "excludeDiscountedFromPercentageOffEntirePurchase" in API call saveCampaign did not work.


Berlin POS version 3.28.2 release notes

6 April 2018

Base version: 3.27.1

Key Features

  • All-in-one receipt printing through EPSI remade in online to use back-office receipts instead of POS local receipt
    • Receipt configuration defined in back-office is now also used in POS
  • Implemented ID-card reading for Atos Worldline terminals (Nixor)

  • Implemented Verifone Finland payments integration (USB device)

New Features

  • Added products assortments support
  • Added configuration parameter,"touchpos_use_customer_coupons_automatically" which applies customer coupons without extra confirmation
  • Added TTD and XCD currencies
  • Added display ads manager URL and token forwarding to customer display application

Improvements

  • On layby/lay-away documents, expiration date can’t be changed on existing document
  • Implemented API request calculateRewardPoints on saveSaleDocument

Fixes

  • Customer search execution with the onscreen keyboard
  • Canceled orders removed
  • Login is not allowed on mobile devices, in case Epsi public token validation is turned on


Erply API version 1.21.8

3 April 2018

New features

  1. API calls verifyUserswitchUser, and changePassword now return the endpoint URL and authentication token for the service that provides advertisements to the point-of-sale customer display. These can be found in the "displayAdManagerURLs" block. There can be multiple endpoints and tokens configured; if that is the case, API clients must pick one.


Erply API version 1.21.7

23 March 2018
  1. Fixed: two issues related to configuration parameter"treat_price_list_discount_as_discount_on_receipt".


Back Office versioon 4.8.5

22 March 2018

22. märts 2018
Antud versiooniuuendus mõjutab vaid neid kontosid, kus kasutatakse väliseid kliendiregistri teenuseid (hetkel vaid üks konto). Rakendatud on kaks muudatust:

  1. Mõne kliendiregistri päringu jaoks on rakendatud vahemällu salvestamine. Vahemällu salvestamist on võimalik konfigureerida parameetritega:
    • "customer_registry_group_getparents_cache_time" = (time in seconds)
    • "customer_registry_customer_getmasterrecord_cache_time" = (time in seconds)
  2. Hinnakirja algoritmi optimeerimine: kui kontol ei kasutata kliendi hinnakirju ja kliendigruppide hinnakirju, saab hinnakirjaotsinguid konfigureerida parameetriga "customer_and_group_price_lists_are_not_used" = 1.


Erply API version 1.21.6

22 March 2018
  1. For accounts that use an external customer registry service, caching has been implemented for some of the customer registry queries. Caching can be enabled with configuration parameters:
    • "customer_registry_group_getparents_cache_time" = (time in seconds)
    • "customer_registry_customer_getmasterrecord_cache_time" = (time in seconds)
  2. Fixed: On a franchise account, an error occurred in API call getProductStock when combining input parameters “getAmountReserved” and “changedSince”.


ERPLY Classic Back Office version 4.8.5

22 March 2018
 This update only affects accounts that use an external customer registry service. (There is one such account at the moment). Two changes have been implemented:
  1. Caching has been implemented for some of the customer registry queries. Caching can be enabled with configuration parameters:
    • "customer_registry_group_getparents_cache_time" = (time in seconds)
    • "customer_registry_customer_getmasterrecord_cache_time" = (time in seconds)
  2. Price list algorithm optimization: if the account is not using customer price lists and customer group price lists, price list lookups can be disabled with configuration parameter "customer_and_group_price_lists_are_not_used" = 1.


Erply API version 1.21.5

19 March 2018
  1. Fixed: API savePurchaseDocument must not return error code 1121 when API client re-saves a confirmed purchase document and does not actually change the document’s type.


Back Office versioon 4.8.4

16 March 2018

16. märts 2018

  • Lisatud on veakõrvaldamise logimise featuur.


Erply API version 1.21.4

16 March 2018
  1. A debug logging feature has been added.


ERPLY Classic Back Office version 4.8.4

16 March 2018
  • A debug logging feature has been added.


Back Office versioon 4.8.3

12 March 2018

12. märts 2018

Täiendused

  1. “Jaekett” -> “Päeva avamised/lõpetamised” all on nüüd võimalik sisestada ka loetud sularaha kogusumma.
    • Kui muuta kogusumma välja, siis väljad “Panka” ja “Jäetud kassasse vahetusrahaks” muudetakse vastavalt sellele automaatselt, sest kogusumma peab võrduma nende kahe lahtri summaga.
    • Ja ka vastupidi – kui muuda välja “Panka” või “Jäetud kassasse vahetusrahaks”, siis ülejäänud kaks välja arvutatakse automaatselt, et klapiks kogusummaga.

Parandused

  1. Parandatud: teatud aruanded, nt “Saldoväljavõte”, kuvas kliendi vana, muudetud nime.


ERPLY Classic Back Office version 4.8.3

12 March 2018

Improvements

  1. The table “Counted amounts by tender” on Day opening and Closing form now additionally allows to enter the total amount of counted cash.
    • Note that when you edit that field, the fields “Deposited” and “Left to till as change” will be updated accordingly, since total counted cash must be equal to the sum of those two fields.
    • And likewise, if you edit either “Deposited”, or “Left to till as change”, the other field will correspondingly be updated to match the total.

Fixes

  1. Fixed: certain reports, eg. the “Balance Report”, displayed customers’ old, historic names.


Back Office versioon 4.8.2

6 March 2018

6. märts 2018

Täiendused

  1. Täiendatud Prantsuse ja Kanada prantsuse tõlkeid

Parandused

  1. Parandatud: teatud juhtudel käsitleti SEB panga laekumiste impordi faili esimest rida valesti, mistõttu sama laekumist võidi järgmisel korral importida topelt.
  2. Parandatud: kasutades eraldiseisvat kliendiregistri liidestust ei kuvata enam halduris veateadet teatud moodulites, kui kasutajal puuduvad õigused näha kliendiregistrit.


ERPLY Classic Back Office version 4.8.2

6 March 2018

Improvements

  1. French and Canadian French translations updated.

Fixes

  1. Fixed: in certain cases, the first line in a SEB bank payment import file was handled incorrectly, which could cause the same payment to be imported again later as a duplicate.
  2. Fixed: when using the integration with a standalone customer registry, back office no longer displays an error page in certain modules if user has no rights to view customer information.


Back Office versioon 4.8.0, 4.8.1

20 February 2018

20. veebruar 2018

  1. “Jaekett” -> “Päeva avamised/lõpetamised” all saab nüüd lugeda summasid ka liigiti ning erinevuse põhjuseid saab redigeerida.
    • Algne info sisestatakse kassas kassiiri poolt. Lisaks sularahale on võimalik lugeda ka teisi makseviise: tšekid, kinkekaardid ning kaardimaksed liikide lõikes (VISA, Discover, deebetkaart, American Express, MasterCard).
    • Valesti sisestatu saab muuta otse vormilt.
    • “Päeva avamised/lõpetamised” vormile on nüüd lisatud “Z-raporti” nupp. Tegemist on kiirvaliku nupuga, mis avab konkreetse kassa z-raporti.
  2. Täiendused kasutajagrupi õigustes. Järgmistele moodulitele saab nüüd eraldi õigusi seadistada:
    • Nopi tooteid tellimusele ja Tellimuse lisamine
    • Laod
    • Kassad
    • Tootegrupid
    • Tooteseeriad
    • Kaubamärgid
    • Parameetrigupid
    • Tarnetingimused


ERPLY Classic Back Office version 4.8.0, 4.8.1

20 February 2018
  1. In Settings → Day Openings and Closings, counted amounts by tender type and variance reasons can now be edited.
    • This information is originally entered by the cashier. In POS, it is possible to count not only cash, but also all other payment types: cheques, gift cards, and card payments by card type (VISA, Discover, debit, American Express, MasterCard).
    • In case the cashier has made a mistake in entering these amounts (or variance reasons), these values can now be edited on the form.
    • On top of the “Day opening and Closing” form, a button “Z Report” has been added. This is a shortcut that opens the respective register’s Z Report. After adjusting the day’s counted values, open the report to verify that it is now correct.
  2. Improvements in user rights. Each of the following modules now has separate user rights:
    • Pick Items and Create an Order
    • Locations
    • Registers
    • Product Groups
    • Product Categories
    • Brands
    • Parameter Groups
    • Delivery Conditions


Erply API version 1.21.2, 1.21.3

20 February 2018
  1. User rights verification in the following API calls has been updated: getBrands, getInventoryRegistrations, getInventoryWriteOffs, getProductCategories, saveBrand, saveDeliveryType, saveProductCategory, saveProductGroup, deleteDeliveryType. This is to ensure compatibility with Classic back office 4.8.0.


Erply API version 1.21.0

14 February 2018

New features

  1. API call getProducts can now return not only price list prices for a particular store, but also information about how these prices were calculated: which price lists applied, in what order, and how much discount each price list provided.
    • To get this information, set input parameter"getPriceCalculationSteps" = 1. For each product, API returns a block of information named"priceCalculationSteps".
    • Since this information is meant to accompany the"priceListPrice" and"priceListPriceWithVat" fields, you also need to set input parameters"getPriceListPrices" = 1 and "warehouseID" (to specify the store).
    • Your account must use Classic back office (version 4.5.0 or newer). On Berlin back office, the feature is not supported yet.
  2. Field"typeID" (payment type ID) has been added to payments returned from API call getFranchiseSalesDocuments.
  3. Input parameter"getCurrentUser" = 1 has been added to API call getUserRights. Setting this flag returns your own user rights (the rights of the currently authenticated user).

Fixes

  1. Fixed: API call getProductGroups returned an error when filters “productGroupID” and “searchAttributeName” were combined.
  2. Fixed: API call getEmployees returned an error when filters “warehouseID” and “searchName” were combined.


Berlin POS version 3.27.1 release notes

12 February 2018

Base version: 3.26.10

New Features

  • Added JS Plugin store integration support
  • Added Argentinian currency peso (ARS)
  • Added VAT number management on company type customers
  • Added price list calculations support in offline when synchronizing documents
  • Added extra parameter to support getting price list calculation steps for quick products and searchable products
  • Added configuration parameter "touchpos_search_customer_on_enter_key_only", which allows execute customer search only by pressing Enter key
  • Added multilingual promotion support if promotions module enabled

Improvements

  • Store correct card names with Cayan payment integration on void or return transactions
  • Removed Zendesk module – not in use anymore
  • Manual discount either document/product based promotions displaying correctly
  • More fields now translatable to all other languages that POS supports

Fixes

  • Allow sell to POS default customer on POS dark theme
  • Fixed product and product groups synchronization for initial login if multilingual POS in use (multi lingual products/product groups/promotions and so on)
  • From plugins stored locally to offline use, now can contain double slash comment lines
  • Fixed price calculation error (may happen), if network quality is not very good

Released with hotfixes (3.26.10)

  • Added override price method on offline mode. Now price can be changed up or down in offline
  • Added image scaling for large images and added canvas width/height for image drawing. This will avoid receipt printing problems with very large logo image files
  • Fixed offline tax calculation where tax was multiplied by row quantity
  • Fixed manual discount usage, if order prices need recalculation by configuration parameter "touchpos_order_pickup_recalculates_prices"
  • Fixed saved sale restore if Applied Manual Discounts module is not installed
  • Get manual discounts for saved sales for completing sale later
  • Added Vietnamese currency Dong (VND) support and option to round VND to nearest 500
  • Fixed payment rounding, where in some cases, calculation is incorrect


ERPLY Berlin Back Office version 5.9.4

12 February 2018

Fixes

  1. A change introduced in 5.9.0 has been rolled back. If user opens a long-running report, they can now no longer browse around in back office until the report has finished loading.


Back Office versioon 4.7.9

7 February 2018

7. veebruar 2018

Täiendused

  1. Halduri poolt tšekile lisatud kaardimakse infole pannakse külge tunnus, mida kassa saab kasutada halduris vaikimisi kaardimakse info asendamiseks terminalist saadud maksetšekiga  (vajalik mõningatel juhtudel Berlin POSi jaoks, nt all-in-one receipt puhul)

Parandused

  1. Parandatud: mõned aruanded võisid kuvada teadet “System update”, kui ei olnud ühtegi kirjet mida kuvada.
  2. Parandatud: frantsiisikontol kuvas “Seaded” -> Kustutatud kirjete logi” all veateadet, kui sortida kirjeid “Aeg” veeru järgi.
  3. Versiooni 4.7.0 muudatus pöörati tagasi. Kui kasutaja avab mahuka aruande, siis seni kuni aruannet genereeritakse ei saa kasutaja kontol ringi liikuda.


ERPLY Classic Back Office version 4.7.9

7 February 2018

Improvements

  1. On a receipt printout, blocks of card payment information are now identifiable by HTML classes. (This is needed for Berlin POS.)

Fixes

  1. Fixed: some reports might have displayed a “System update” message if there were no records to display.
  2. Fixed: on a franchise account, in the “Settings → Log of deleted items” module, clicking on the “Time” column to sort records by time produced an error.
  3. A change introduced in 4.7.0 has been rolled back. If user opens a long-running report, they can now no longer browse around in back office until the report has finished loading.


ERPLY Berlin Back Office version 5.9.3

5 February 2018

Fixes

  1. Fixed: the Show only items in stock“ check box in Inventory → Inventory was disabled by mistake.
  2. Fixed: opening a deleted sales document, purchase document or customer card (by directly supplying its ID) will now correctly inform that this record no longer exists. Additionally, opening a deleted sales document might have formerly produced a “System update“ message.
  3. Fixed: “Timeclock entries“ table did not show records that were not associated with an employee.
  4. Fixed: in case a timeclock record has a missing start time or end time, the Time and Attendance Report will now leave the amount of hours empty, instead of reporting a huge value.
  5. Fixed: The “Recipe“ window on a bundle product or assembly product card will now list all components, not only the first 20.
  6. Fixed: In the “Recipe“ dialog, columns are now resizable.


ERPLY Berlin Back Office version 5.9.2

25 January 2018
  1. The Customers → “Export Customers” and PIM → “Export Products” pages now have an updated design.
  2. Configuration parameter "overwrite_price_decimals" is now supported on Berlin back office. (It already existed in Classic back office.) It can be used to customize the precision of a product’s net price.
    • In US, net prices are by default with 2 decimal places and it is not recommended to change that.
    • The setting may be needed on Canadian accounts, however.
    • On European accounts, prices are by default with 4 decimal places. This configuration parameter may be used to increase or decrease it.
    • Calculation of prices, discounts, and invoice totals is affected by many other aspects, not only this parameter. Before using, please consult with customer support.
  3. Greek translations have been updated.


Back Office versioon 4.7.7 - 4.7.8

22 January 2018

22. jaanuar 2018

  • Javascripti pluginatele on lisatud muutuja “country” (sisaldab kahetähelist konto riigi tähist)


ERPLY Classic Back Office version 4.7.7 - 4.7.8

22 January 2018
  • For Javascript plugins, global variable"country" has been added (containing the two-letter code of account’s country).


Back Office versioon 4.7.5 - 4.7.6

19 January 2018

19. jaanuar 2018

  • Prantsuse ja Kanada tõlked uuendatud


ERPLY Berlin Back Office version 5.9.0, 5.9.1

19 January 2018

New features

“Store Regions” module

  • This feature allows to group stores into “regions”, and set up price lists that apply to an entire group of stores.
  • Please contact customer support to enable it on your account.
  • Store Regions can be managed in Retail Chain → Store regions. On location form, you can specify which region the store belongs to. Locations can also be filtered by region.
  • A region can be associated with an unlimited number of price lists, and you can change the order in which the price lists will apply. These price lists will apply to all stores in the region.
  • It is also possible to define store region and customer group-specific price lists: price lists that apply only in the specified region, and to customers belonging to the specified group.
  • Price lists will be applied in the following order (and each successive price list overrides a previous one if they contain the same products):
    1. Region price lists;
    2. Region and customer group-specific price lists;
    3. Location price lists.
  • A region cannot be deleted if there is at least one store that belongs to that region.
  • On User form and Employee form, the lists of locations additionally show region name for each location. Similarly, the “Locations and tax rates” block on Product Group form, too, has been augmented with region names.
  • For region-related API calls, see the release notes for API version 1.13.0, or the documentation of API call “getStoreRegions”. This page contains links to all other related API calls.

Other new features

  1. On a sales document, rows can now be dragged to adjust their order.
  2. Sales documents now properly support different currencies.
    • Item prices in product search are displayed in the selected currency;
    • Changing the currency will recalculate item prices on the document;
    • Cost and markup are shown and calculated correctly regardless of selected currency.
  3. ERPLY now supports creating invoices with Reverse VAT (VAT that needs to be paid by the buyer).
    • Reverse VAT needs to be defined as a separate tax rate in the Settings → Set up tax rates module.
    • On sales document printout, Reverse VAT is reported in a separate block.
    • The description text which appears next to the Reverse VAT amount on the printout (instructions to the buyer) can be customized in Settings → Configuration.
    • In Estonia, an invoice is not allowed to contain mixed regular and reverse VAT, or different reverse VAT rates. Items with regular VAT and reverse VAT need to be put on separate invoices.
  4. Back office will no longer allow direct access from POS if you have originally logged into POS with a PIN, and will prompt for your user name and password. This restriction has been implemented to improve back office’s security.
  5. New module Inventory → “Pick items to create an order” has been added. It is a convenient way to browse the product catalog and pick items to a “shopping cart”, which can then be turned into a sales order or a purchase order. It can be useful when taking phone orders — or for doing inventory restocking. For each product, ERPLY can show current quantities in various stores, period sales and purchases, amount already on order (or being transferred from other stores), and list price for a specific customer.
  6. Excel / CSV output option has been added for the following reports:
    • “Payments Summary (Cash Audit)” and “Payments by date”;
    • Reports → Commission and timeclock → Time and Attendance Report.
  7. Configuration parameters "password_only_alphanumeric_allowed" and "password_alphanumeric_required" have been added. With these parameters, it is possible to restrict what kinds of passwords users can pick. (The first parameter will disallow any characters besides letters and numbers; the second requires a password to contain at least one small letter, one capital letter and one digit.)

Improvements

  1. If user opens a long-running report, it should no longer lock up the whole back office for them. While a report is being prepared, it is now possible to continue browsing around in other modules.
  2. French and Canadian French translations have been updated.
  3. The “Supplier” field on forms has been changed from a drop-down to a text field with integrated search, to better support accounts with a very large number of suppliers.
  4. Both “location in warehouse” fields on product card (the drop-down, and the text field) can now be exported and imported with product export and product import modules.
  5. Nordea Bank has been renamed to Luminor.
  6. Fields “netPrice” and “originalNetPrice” on Actual Reports product labels now have the same precision as the “Net Price” field on product card.
  7. On new South African accounts, Invoice-Waybills will be called “Tax Invoice-Waybills”. (Receipts have been renamed to “Receipt / Tax Invoice” and credit invoices to “Credit Tax Invoice”.)
  8. Old Web POS (the point-of-sale application with light grey interface and grey buttons) is unused and has been removed.
  9. Web POS (the point-of-sale application with grey interface and colored buttons) has been deprecated; the application now reports that it is outdated and will be removed soon. We recommend to migrate to Berlin POS.
  10. For Javascript plugins, global variable "country" has been added (containing the two-letter code of account’s country).

Fixes

  1. Fixed: a product’s “reserved quantity” did not include quantities reserved with Inventory Transfer Orders.
  2. Fixed: “Previous” & “Next” buttons on product card did not work.
  3. Fixed: Reports “Sales by product group, with drill down” and “Sales by category, with drill down” were sometimes splitting a single product group or product category into multiple lines.
  4. Fixed: The red dot on purchase document rows (which indicates a changed price) now takes less space and no longer covers the price field.
  5. When replacing a product on a sales document, the “Keep window open” check box in the product search dialog is now disabled. Keeping the window open and selecting multiple products is possible only when adding new items to the end of the sales document (not when replacing an existing item in the middle of the document).
  6. Security fixes.


ERPLY Classic Back Office version 4.7.5 - 4.7.6

19 January 2018
  • French and Canadian French translations updated.


Erply API version 1.20.0

12 January 2018

New features

  1. API call verifyUser no longer allows PIN authentication. For an alternative, please see the switchUser call. It requires the previous session’s key as input, meaning that authenticating with a PIN is possible only if another user has been previously logged into your application.
  2. Authentication calls (verifyUserswitchUser and changePassword) now enforce a maximum session length of 1 day (86400 seconds). If you request a session longer than that, API will still generate a session that expires in 86400 seconds.
  3. Support for a customer registry microservice has been added.
  4. Feature “Minimum Password Age” has been implemented. This feature may be used to limit how often regular (non-administrator) users can change their password (eg. no more frequently than once every 5 days).
    • This feature can be enabled by setting configuration parameter "minimum_password_age" to the desired number of days.
    • The corresponding implementation for Classic back office will be added in version 4.7.0.

Improvements

  1. In sign-up e-mails, support contact information for Finland has been updated.
  2. An optimization in API call getSalesDocuments.

Fixes

  1. Fixed: API call getAmountsOnOrder returned incorrect quantities.
  2. Fixed: API call editAssortmentProducts incorrectly reported that a product does not exist in the assortment.


ERPLY Classic Back Office version 4.7.0 - 4.7.4

12 January 2018

New features

  1. Product labels can now be printed from a sales document, Inventory Registration or an Inventory Transfer, too. (Formerly, it was only possible to print product labels from a purchase document.)
  2. The “Warehouse Report” on product card (list of transactions made with that product, and its current amount in stock) has been reordered. Current inventory quantities are now listed first. The list of transactions comes after that, ordered chronologically with newest transactions at the top (not oldest ones at the top, as before).
  3. In Settings → Configuration → Sending invoices by e-mail, it is now possible to specify whether an invoice should by default be e-mailed to the customer, to the payer, or both. (Or, depending on account configuration: to the customer, to the recipient of goods, or both).
  4. Back office will no longer allow direct access from POS if you have originally logged into POS with a PIN, and will prompt for your user name and password. This restriction has been implemented to improve back office’s security.
  5. New module “Optionally Disable Promotions” has been added. This is an extra feature that adds a check box to sales promotion form: “Enabled – this promotion can be applied”. Clearing the check box offers an additional way to instantly deactivate a promotion (aside from changing its type, or modifying start and end dates).
    • Please contact customer support to enable it on your account.
  6. Actual Reports printouts for sales documents can now contain information about Reverse VAT; the respective fields have been added to the data set of sales documents.
  7. Receipt footer can now be customized by store. Field “Message in receipt footer” has been added to location form. Store-specific footer text will override the general text specified in Settings → Configuration → Receipt printouts.
  8. At the top of every form, the creation time, creator’s name, last modification time and last modifier’s name are now displayed — similarly to how this information has been presented on Location or User form, for example. (This information bar does not appear on versioned records, eg. on a sales document or on customer card, because these forms have a drop-down list of all changes.)
  9. Feature “Minimum Password Age” has been implemented. This feature can be used to limit how often regular (non-administrator) users can change their password; eg. no more frequently than once every 5 days.
    • This feature can be enabled by setting configuration parameter "minimum_password_age" to the desired number of days.
  10. Old Web POS (the point-of-sale application with light grey interface and grey buttons) has been deprecated; the application now reports that it is outdated and will be removed soon. We recommend to migrate to Berlin POS.
  11. Configuration setting "additional_payment_type_system_codes" has been added, to be able to define custom “system codes” for payment types.
  12. Support for a customer registry microservice has been added.

Improvements

  1. If user opens a long-running report, it should no longer lock up the whole back office for them. While a report is being prepared, it is now possible to continue browsing around in other modules.
  2. Vietnamese language option, and Vietnamese translation has been added. It can be enabled on Vietnamese accounts by customer support.
  3. Lithuanian translations have been updated.
  4. Latvian translations have been updated.
  5. Column “Supplier on the act” has been added to Inventory Registrations Report.
  6. Column “Recipient on the act” has been added to Inventory Write-Offs Report.
  7. Inventory Registrations Report is now grouped by reason code (if the respective extra module has been enabled), similarly to the Inventory Write-Offs Report.
  8. From Location form, it is now possible to open the store’s price lists.
  9. Fields “netPrice” and “originalNetPrice” on Actual Reports product labels now have the same precision as the “Net Price” field on product card.
  10. Nordea Bank has been renamed to Luminor.
  11. On new South African accounts, Invoice-Waybills will be called “Tax Invoice-Waybills”. (Receipts have been renamed to “Receipt / Tax Invoice” and credit invoices to “Credit Tax Invoice”.)
  12. Non-functional “Check e-mail” button has been removed from the Documents module.
  13. Franchise-related improvements.
  14. The “Help & About” → “ERPLY Terms of Service” link on Finnish accounts has been updated.

Fixes

  1. Fixed: Sales receipts did not correctly display amount paid by customer’s store credit.
  2. Fixed: Incorrect grouping and missing subtotals in Reports → Sales Promotions → Sales Promotions Report have been fixed.
  3. Fixed: Price list and manual discounts were showing up on the Sales Promotions Report.
  4. Fixed: when 10 or more follow-up orders had been created from a Sales Order (through the “Partial fulfilment splits sales order” feature), all the following orders received the same "-10" number suffix, instead of each successive document getting a new suffix.
  5. Fixed: the “last modification time” of a product group, product category or customer group was not updated when it was dragged to a different place in the hierarchy tree.
  6. Fixed: on a price list form, clicking the “Total number of results” button did not display the correct number of products in that price list.
  7. Fixed: when using the “Alcohol wholesale” extra module, and deleting a batch from product card, re-saving a sales invoice where that batch had been used will no longer discard batch information from that invoice row.
  8. Fixed: shift-clicking (to select a range of products) in the product catalog did not work with matrix variations.
  9. Fixed: if a price list is deleted, it will no longer remain visible in back office, on Store Region form, in the “Store region price lists” tab, as an empty line.
  10. Fixed: purchase invoice form will no longer display an error if all “Units” (units of products) have been deleted from the account.
  11. Fixed: if the setting Settings → Configuration → Inventory and Purchase → “Inventory Transfer Order removes items from inventory” has been enabled in the past, but is then disabled again, deleting a Transfer Order that has been created during the interim period will no longer leave orphaned inventory records in the system.
  12. Security fixes.


Back Office versioon 4.7.0 - 4.7.4

12 January 2018

12. jaanuar 2018

Uued võimalused

  1. Toote etikette saab nüüd trükkida ka otse müügidokumentidelt, arvelevõtmise aktidelt või laoliikumistelt. (Varem sai trükkida vaid otse ostudokumentidelt).
  2. Toote laoaruandes kuvatav info on nüüd ümber pööratud, võimaldades esmajärjekorras kuvada toote kõige värskem ajalugu. (Varem kuvati kõige hilisem esimesena ning uue info nägemiseks tuli kerida kõige alla).
  3. “Seaded” -> “Konfiguratsioonid” -> “Arvete saatmine e-mailiga” all on nüüd võimalik täpsustada, kas arve saadetakse vaikimisi kliendile, maksjale või mõlemale. (Olenevalt konto seadistusest võib valikus olla ka kliendile, kauba saajale või mõlemale).
  4. Turvalisuse kaalutlustel ei ole enam võimalik kassast otse haldurisse ligi pääseda, kui kasutaja on kassasse sisse logitud PIN koodiga. Haldurisse pääsemiseks tuleb kasutajal täiendavalt sisestada oma kasutajanimi ja parool.
  5. Lisatud on uus moodul “Optionally Disable Promotions”, millega on võimalik kampaaniate puhul lihtsamini määrata, kas kampaania rakendub või mitte.  Tegemist on täiendava seadistusvõimalusega, lisaks kampaania tüübi või algus- ja lõpukuupäevade muutmisele.
    – Seadistuse saab aktiveerida kasutajatugi.
  6. Kohandatud väljatrükkidele saab nüüd lisada infot ka pöördkäibemaksu kohta. Vastavad väljad on lisatud kohandatud väljatrüki andmekogumisse.
  7. Sularahaarve jalust saab nüüd kohandada ladude kaupa. Selleks on väljale “Tekst arve jaluses” lisatud lao valik. Laospetsiifiline jalus kirjutab üle üldise teksti “Seaded” -> “Üldseadistused” -> “Arvete väljatrükid”. 
  8. Sarnaselt kasutajakaardile või laokaardile, kuvatakse nüüd kirje loomise aeg, looja kasutajanimi ning viimase muudatuse aeg ja muutja kasutajanimi välja ülemisel äärel. Kuvatakse ainult esimest ja viimast kirjet; arvete ja kliendikaardi ajaloole sarnast rippmenüüd kõikidest muudatustest ei kuvata. 
  9. Lisatud on uus funktsionaalsus “Parooli minimaalne vanus”, mis võimaldab määrata, kui tihti kasutajad (mitte-administraatorid) oma parooli peaksid vahetama; mitte tihemini kui iga 5 päeva tagant.
    – Seadistuse saab aktiveerida ning soovitud päevade arvu seadistada konfiguratsiooniparameetriga “minimum_password_age”.
  10. Vana Web POS (valge tausta ja hallide nuppudega kassa) on iganenud ning selle kasutamisel kuvatakse kasutajale teadet selle peatsest sulgemisest. Soovitame üle minna Berlin POS versioonile. Abi seadistamise ning juhistega saab klienditoelt. 
  11. Lisatud on konfigutasiooniseadistus “additional_payment_type_system_codes”, mis võimaldab lisada makseviisidele kohandatud süsteemikoode.
  12. Lisatud on tugi kliendi registreerimise mikroteenusel.

Edasiarendused

  1. Mahukamat aruannet avades ei tohiks enam kogu haldur lukku minna.  Nüüd on võimalik oma tööd jätkata, samal ajal kui aruannet genereeritakse.
  2. Lisatud on vietnami keel. Kasutajatugi saab keele saab aktiveerida Vietnami kontodel.
  3. Uuendatud on leedukeelsed tõlked.
  4. Uuendatud on lätikeelsed tõlked.
  5. Arvelevõtmiste koond aruandesse on lisatud hankija veerg.
  6. Mahakandmiste koond aruandesse on lisatud hankija veerg.
  7. Arvelevõtmiste koond aruannet on nüüd võimalik grupeerida põhjuskoodide järgi (vajab spetsiaalse mooduli aktiveerimist), sarnaselt mahakandmiste koond aruandele.
  8. Kaupluse hinnakirja on nüüd võimalik avada otse Lao kaardilt.
  9. Kohandatud väljatrüki väljad “netPrice” ja “originalNetPrice” kasutavad nüüd tootekaardil oleva netohinnaga sama täpsust.
  10. Nordea pank nimetati ringi Luminor.
  11. Uutel Lõuna-Aafrika kontodel on Arve-saatelehed ringi nimetatud “Tax Invoice-Waybill”´iks. Sularahaarved on nüüd “Receipt / Tax Invoice” ja kreeditarved “Credit Tax Invoice”.
  12. Dokumentide moodulist eemaldati “Kontrolli e-maili”, millel polnud eraldi funktsionaalsust.
  13. Frantsiisiga seotud täiendused.
  14. Soome kontodel on uuendatud “Help & About” -> “ERPLY Terms of Service” all olevaid kasutustingimusi.

Parandused

  1. Parandatud: Sularahaarved ei kuvanud arvelduskrediidiga tasutud summat korrektselt.
  2. Parandatud: Vale rühmitus ja puuduvad vahesummad  “Aruanded” -> “Müügikampaaniad” -> “Kampaaniate aruanne” all.
  3. Parandatud: Kampaaniate aruanne kuvas hinnakirju ja käsitsi tehtud allahindluseid.
  4. Parandatud: Kümne ja enama järeltellimuse puhul (Üldseadistuse parameeter “Müügitellimuse osalisel täitmisel tellimus poolitatakse”) määrati müügitellimusele sama sufiks “-10”, selle asemel et iga tellimus saaks järjekorras järgmise sufiksi.
  5. Parandatud: Tootegrupi, tooteseeria ja kliendigrupi kausta liigutamisel hierarhiapuul ei uuendatud “viimati uuendatud” kirjet.
  6. Parandatud: Klikates hinnakirjas “Kirjeid kokku” ei kuvatud korrektselt hinnakirjas olevate toodete koguarvu.
  7. Parandatud: Kustutades tootekaardil oleva alkopartii (Alkoversiooni eriseadistus) ei kustuta see enam partii infot olemasoleva müügiarve üle salvestamisel.
  8. Parandatud: Maatrikstoodete puhul ei töötanud tootekataloogis shift-nupu kasutamine toodete vahemiku märkimiseks.
  9. Parandatud: Kustutades hinnakirja ei ole see enam halduris piirkonna hinnakirjana nähtav.
  10. Parandatud: Ostuarve ei anna enam veateadet kui kõik tooteühikud kontol on kustutatud.
  11. Parandatud: Kui Üldseadetes olev seadistus “Lao liikumise tellimus võtab kaubad laost maha” on minevikus aktiveeritud ning seejärel uuesti deaktiveeritud, siis kustutades laoliikumise tellimuse aktiveeritud perioodist ei jäta enam süsteemi peidetud laokoguseid.
  12. Turvalisuse parandused.


Erply API version 1.19.1

18 December 2017
  • Security fix.


Erply API version 1.19.0

5 December 2017

New features

  • New API call getBilledUntilDate has been added. This API call returns the “last billed date” for recurring billings (the same information that can also be seen in back office, Sales → Recurring billings).

Improvements

  • Improved backward compatibility: to have API response returned with an appropriate "Content-Type" header (which was originally added in 1.18.0), API client must now explicitly add input parameter "sendContentType" = 1 to every request. Changing Content-Type for all requests had an adverse effect on existing API clients.
  • As a performance optimization, API call calculateShoppingCart will no longer:
    • Apply item-level promotion discounts (get $ or % off of a specific product) to rows with quantity 5000 or over. (Price list prices and invoice-level discounts — $ or % off entire sale — will still apply.)
    • Allow rows with quantity 5000 or over to trigger a promotion. (Promotion “Buy Product X and get 10% off entire sale” will not apply if you set the quantity of Product X to 5000.)
    • Processing a large quantity requires more server resources and may be slow. In the “calculateShoppingCart” requests sent from POS, a large quantity is usually a cashier’s typo, for example a product code scanned into the Quantity field. Thus, this change ensures that a mistyped quantity will not make POS unresponsive.
  • Fields "addedByUserName" and "lastModifiedByUserName" have been added to API call getPriceLists.
  • Field "batch" has been added to API calls getSalesDocuments and saveSalesDocument, to each document row. It is related to extra module “Alcohol Wholesale”. To be able to use this field in API, this extra module must be activated on your account. (This field was formerly visible in back office, on sales document form, but was not editable over API.)
  • Support for Vietnamese language has been added. However, to use Vietnamese, account must be updated to a back office version that supports Vietnamese. Vietnamese support is coming in Classic back office 4.7.
  • Support for “subsidies” (originally added in API version 1.13.0) has been improved. In API “saveSalesDocument” call, subsidy now gets calculated and stored for “Get these items for a special price” promotions, too.

Fixes

  • Fixed: API call getSalesDocuments now returns a reference number for Sales Orders, too. Formerly, Sales Orders printed from back office did have a reference number, but API did not output it.
  • Fixed: errors in API calls “getSchedule”, “getTimeSlots” and “saveEvent” have been fixed.
  • Fixed: API call “saveSalesDocument” will no longer attach manual discount’s reason ID to discount records that are not manual discounts (ie., to price list and promotion discounts). This issue might have been observable when retrieving discount records with API getAppliedPromotionRecords call.
  • Fixed: products that have a product card price 0.00, but for which a price has been defined in a store price list, were incorrectly flagged by API getSalesDocuments as "originalPriceIsZero" = 1.
  • Fixed: after calling saveCompanyInfo and saveAddress simultaneously, attempting to edit company information in back office sometimes failed with an error, “This form has been updated by another user.”.
  • Fixed: calling getProductStock with the parameters "getProductsWithReorderPointDefined" = 1 or "getProductsWithRestockLevelDefined" = 1 did not return products with which no inventory transactions had taken place yet.
  • Fixed: according to documentation, saveSalesDocument is supposed to apply store- and customer-specific price (and discount) when omitting "price#" and "discount#" input parameters. This did not work if product’s original price on product card was 0 and its price had been specified in a price list.


ERPLY Berlin Back Office version 5.8.0

30 November 2017

New features

  • The back office now displays a notification if a version upgrade has taken place.
  • When adding products to a sales document, the product search dialog now allows to pick multiple items. A new check box, titled “Keep window open”, has been added to the dialog. If you check this box, selecting a product will not dismiss the search window. The window will stay open, and will allow to select more items, or even to run a new search.
  • “Contact Us” menu option has been added into the top right corner menu; clicking this link will open a box with customer support phone number and e-mail address.
  • “Prepayment VAT” has been added to the printouts of standard prepayment invoices.
  • On sales documents that have been created from Assignments, a link to the original Assignment is now displayed on the yellow bar at the top of the page.
  • In Settings → Configuration → Matrix Products, it is now possible to specify that product code 3 … code 8 should also be updated on all matrix variations when you change the code on the parent product.

Improvements

  • French translations have been added. French can be enabled on French and Canadian accounts by customer support.
  • Latvian translations have been updated.
  • A few Lithuanian translations have been corrected.
  • On confirmed Invoice-Waybills, Waybills, Receipts and Credit Invoices, product names (ie., item descriptions that appear on the printout) can now be edited.
    • On other types of sales documents, and on unconfirmed invoices, it has already been possible to edit an item’s description. (Every edit will trigger the product search dialog, but this can be dismissed.) On confirmed documents, it was not possible to edit the description at all; this restriction has been lifted.
  • When using the Assignments module, back office automatically generates a sales document, with type “Lay-by” or “Layaway”, for each Assignment, to ensure that products on the assignments will be reserved in stock. These automatically generated documents are no longer displayed in the Invoices module. (Back office manages them automatically and these documents should not be edited by hand.)
  • Field “privateNotes” is now available on Actual Reports sales document printouts.
  • Search field “Payer” (which searches by the payer’s name imported from bank) has been added to Sales → Payments.
  • Report generator: fields “Received Purchase Orders (Our no.)” and “Received Purchase Orders (Tracking no.)” have been added to purchase invoices.
  • A few optimizations in physical stocktaking.

Fixes

  • Fixed: Deleting a line from a sales document caused some of the subsequent edits to apply to wrong lines.
  • Fixed: on a sales document, adding multiple matrix variations in the middle of the document will no longer overwrite the following rows.
  • Fixed: on a franchise account, it was not possible to change a user’s password.
  • Fixed: it was not possible to delete the first product group discount from a price list.
  • Fixed: when creating a sales document from an Assignment, VAT was applied to the prices twice.
  • Fixed: when switching customer on an Assignment, prices of parts and repairs unnecessarily changed in certain cases.
  • Fixed: if a Waybill had been created from an Assignment, ERPLY did not allow to make an Invoice from that Waybill.
  • Fixed: when a Sales Order had been created from an Assignment, and an Invoice was created from that Order, the Order continued to reserve goods and the Orders module displayed duplicate references to the created invoice.
  • Fixed: it was not possible to use date format “dd-mm-yyyy”; any date entered into a date field, or picked from the mini-calendar, got corrupted.
  • Fixed: back office will now display an error message when user saves a document and an invalid date has been entered on the form. (Previously, not catching that error might have resulted in a document being created without a date.)
  • Fixed: on iPhone, numeric fields did not allow to enter negative numbers, because the keyboard that appeared did not contain a “minus” key. (Now, a more complete keyboard appears for these fields.)
  • Fixed: Sales totals on Stock Replenishment Report were not linked to a sales report.
  • Fixed: it was not possible to update an address on Customer form, if the check box “Use POS with touchscreen interface” in Settings → Configuration was unchecked.
  • Fixed: when opening a purchase invoice or product card from Purchase Report, it was not possible to save any edits in that window.
  • Fixed: When printing a Purchase Invoice or Purchase Order in a foreign language, “free-text items” did not have a name. The “Product” column was blank.
  • Fixed: When printing out multiple sales documents, they were occasionally printed on top of each other.
  • Fixed: Incorrect label in Sales Orders module. A filter was labeled “Invoice payer” when it should have actually been “Ship To”.
  • Fixed: reordering product groups, or product categories, by dragging them around in the tree did not update the product group’s or category’s “last modification time” time stamp.
  • Fixed: Payment import from SEB, Swedbank and LHV (Estonia): now a payment will be imported even if the line does not contain payer’s account number, only payer name.


Erply API version 1.18.0

9 November 2017

New features

  • New API call getRoundedSales has been added. It returns a list of invoices, receipts, invoice-waybills and credit invoices where invoice total has been rounded.
    • Rounding can be configured from back office: Settings → Configuration → Invoices and sales. Invoices can be rounded to the nearest 0.05, nearest 0.10, or full units.
    • In certain countries, sales paid in cash are rounded to the nearest 0.05, too.
  • Promotions can now be “enabled” and “disabled” with a check box (in addition to adjusting start and end dates). Field "enabled" has been added to API calls saveCampaign and getCampaigns.
    • This feature needs to be activated by customer support. Please contact customer support if you need this feature.
    • Additionally, it requires Classic back office version 4.7.0 or newer.

Improvements

  • API responses are now returned with an appropriate “Content-Type” HTTP header:
    • “application/json” for JSON output;
    • “application/xml” for XML output.
  • Field "storeGroup" has been added to API call getCampaigns.
  • In API call saveCampaign, the default value for input parameter "type" is now "auto".
  • One new partner key added.
  • A hardcoded customer-specific setting removed.

Fixes

  • Fixed: promotion settings “Each customer can use the promotion only once” and “Promotion can only be used once on every birthday” were not being respected. This was a regression introduced in API version 1.13.0.
  • Fixed: an error in API call saveAddressType.
  • Fixed: Promotions marked with the check box “Allow the same items to trigger other promotions after this promotion has been applied” were in some cases being applied to the sale too many times.


Back Office versioon 4.6.0

8 November 2017

8. november 2017

Uued võimalused

  1. Ettemaksuarvete standard väljatrükkidel kuvatakse nüüd ettemaksuarve käibemaksu.
  2. Nüüd on võimalik läbi kohandatud väljatrüki kuvada müügidokumentidele käibemaksu komponentide kaupa – st igal müügidokumendi real ning arvel kokku. Komponentideks võivad näiteks olla USA-s kasutusel olevad riigi, maakonna või linna maksud; GST ja PST Kanadas; või CGST, SGST ja IGST Indias.
    1. Seadistuse kasutamiseks tuleb aktiveerida “City, county and state tax rates” moodul, selleks võtke ühendust kasutajatoega.
  3. Lisatud on konfiguratsiooniparameeter “unsuccessful_login_lockout_duration”, millega saab määrata, mitmeks minutiks kasutaja ligipääs Erplyle piiratakse korduva ebaõnnestunud sisselogimise korral. Vaikimisi blokeeritakse ligipääs 15-minutiks.

Edasiarendused

  • Eemaldatud on üks spetsiifiline kliendikohane seadistus

Parandused

  • Parandatud: Kui kasutajale ei ole antud õigust lisada töökäske, siis ei peaks ta ka saama lisada töökäsule tooteid.


ERPLY Classic Back Office version 4.6.0

8 November 2017

New features

  • “Prepayment VAT” has been added to the printouts of standard prepayment invoices.
  • On Actual Reports sales document printouts, it is now possible to show amount of tax “by component” – on each sales document row, as well as totals for the whole document. These “components” might be, for instance: state, city, and county sales taxes in the United States; GST and PST in Canada; or CGST, SGST and IGST in India.
    • To use that feature, the “City, county and state tax rates” module needs to be installed on your account. If you do not have it on your account please contact customer support.
  • Configuration parameter "unsuccessful_login_lockout_duration" has been added, to adjust how many minutes a user should be locked out of the system, after repeated unsuccessful log-in attempts. By default, the lock-out time is 15 minutes.

Improvements

  • A hardcoded customer-specific setting removed.

Fixes

  • Fixed: When a user does not have a permission to edit an Assignment, then the user should not be allowed to add products/services to the assignment.


Erply API version 1.17.1

31 October 2017

Fixes

  • Fixed: when re-saving a sales or purchase document with API calls saveSalesDocument or savePurchaseDocument, and only updating/setting an attribute or some other field (without updating document rows), package quantities on rows were lost.
  • Fixed: when re-saving a sales document with API call saveSalesDocument, the “Billing period” information on invoice (start and end date) was lost.
  • Fixed: API calls saveProductGroup and saveProductCategory no longer allow to set a group as its own parent.
  • Fixed: API call saveSalesDocument returned an error when saving a receipt with promotion information and a manual discount.
  • Fixed: API call getProductStock returned an error when using input parameters "getProductsWithReorderPointDefined" = 1 or "getProductsWithRestockLevelDefined" = 1.


Back Office versioon 4.5.0 - 4.5.1

23 October 2017

23. oktoober 2017

Uued võimalused

  1. Poe regioonide moodul

    1. See funktsioon lubab grupeerida kaupluseid regioonide järgi ning rakendada hinnakirju tervele kaupluste grupile.
    2. Mooduli aktiveerimiseks võtke ühendust klienditoega.
    3. Kaupluste regioonid on hallatavad Jaekett→ Kaupluste regioonid alt. Lao/kaupluse vormil saab määrata, millisesse regiooni kauplus kuulub.
    4. Regiooni saab siduda mitme hinnakirjaga, hinnakirjade järjestust saab muuta.
    5. Samuti on võimalik määrata hinnakiri, mis rakendub samal ajal nii konkreetsele regioonile kui ka kliendigrupile: hinnakiri, mis rakendub poe regioonis kirjeldatud ladudele ning klientidele, kes kuuluvad konkreetsesse kliendigruppi.
    6. Hinnakirjad rakenduvad alljärgnevas järjekorras (ning iga järgnev hinnakiri kirjutab üle eelmise hinnakirja toote hinna, kui tegemist on sama tootega):
      1. Regiooni hinnakiri;
      2. Regiooni ja kliendigrupi spetsiifiline hinnakiri;
      3. Lao/kaupluse hinnakiri.
    7. Regiooni ei saa kustutada kui sinna kuulub vähemalt üks pood.
    8. Ladu → Laod/kauplused alla on lisatud uus nupp: “Järjesta regiooniti”, millele klikates järjestatakse laod/kauplused regiooniti ja tähestikuliselt (Regioonisiseselt säilitatakse kaupluste eelnev järjestus).
    9. Regioonikohaste API päringute kohta vaata lähemalt API 1.13.0 versiooni uuenduse infot https://erply.com/release-notes/?c=65
  2. Müügikampaaniate piiramine teatud regioonidele ja/või kliendigruppidele

    1. Funktsioon võimaldab täpsustada, millisele regioonile ja/või kliendigrupile müügikampaania rakenduma peab.
    2. Aktiveerimiseks võtke ühendust klienditoega. Mooduli aktiveerimiseks on tarvilik ka eelmises punktis kirjeldatud kaupluste regioonide moodul.
    3. Funktsiooni aktiveerimisel tekivad müügikampaania vormile kaks välja:
      1. [Kampaania rakendub ainult] … nendes kaupluste regioonides:
      2. Kampaania rakendub ainult nendel kliendigruppidel:
    4. Võimalik on selekteerida mitut regiooni ja kliendigruppi.
  3. Kassatšekkide väljatrükid üldseadetes

    • Seaded → Üldseaded alla on lisatud kassatšekkide väljatrükke reguleerivad sättevõimalused (alajaotuses “Kassatšekkide väljatrükid”).
    • Näiteks on nüüd võimalik täita sellised väljad nagu:
      • Kasutatud kupongid;
      • Kaardimaksed, detailselt / Kaardimaksed, lühendatult (neid kahte valikut ei ole USA ja Kanada kontodel – nendes riikides on kaardi makseinfo arvetel eeldefineeritud. Kuid need seadistusvõimalused võivad olla kasulikud teistes riikides);
      • Kliendikaardi kood;
      • Tagastuse või allahindluse põhjuskood;
      • Teenindaja nimi:
      • Kliendi nimi;
      • Kliendi aadress;
      • Alghind;
    • Nende seas ka täiesti uued võimalused:
      • Võimalus kustutada kliendi nimi kassatšeki väljatrükilt (juhul, kui soovitakse näha vaid kliendikaardi numbrit);
      • Maksuvabastuse number;
      • Valuutakurss välisvaluutas maksetele;
      • Rida summaarse allahindlusega (kui klient sai soodustust) saab nüüd olla kirjeldatud kolmes erinevas keeles (eesti, inglise, vene).
  4. Allahindluste kuvamine tšekil

    • Kassatšekkide väljatrükke saab seadistada nii, et kuvatakse rida rea haaval informatsiooni tehtud allahindluste kohta. Seaded → Üldseadistused → Kassatšeki väljatrükk alt saab valida, kas tšekile trükitakse:
      • Müügikampaaniate allahindlus;
      • Hinnakirjade allahindlus;
      • Käsitsi tehtav allahindlus.
    • Iga käsitsi tehtud allahindluse kohta kuvatakse tšekil:

    1) Allahindluse nimetus (nt Hinnakirja nimi/Müügikampaania nimi/manuaalse allahindluse põhjuskood või põhjuskoodi puudumisel “Käsitsi allahindlus”);
    2) Mitmele tootele allahindlus rakendus;
    3) Allahindlus tooteühiku kohta.

    • Käsitsi tehtava allahindluse ja hinnakirja allahindluse valikute nägemiseks võtke ühendust klienditoega.
    • Detailne allahindluste kohane informatsioon võib olla vajalik integratsioonide puhul. Antud info läbi API saamiseks palun tutvuge API dokumentatsiooniga. Päringu nimi on “getAppliedPromotionRecords”.
  5. Sortimentide moodul

    • Antud versiooniuuendus on ettevalmistus”Sortimentide” moodulile, st võimalus määratleda erinevaid tooteid erinevatele kauplustele.
    • Mooduli aktiveerimiseks võtke ühendust klienditoega.
    • Moodul ei ole hetkel veel töökorras. On vaid võimalus defineerida sortimendid ning muuta nende sisu, kuid hetkel need veel ei rakendu. Kõiki tooteid on võimalik kassas ja halduris müüa ja osta tavapäraselt, hoolimata sellest, kas nad konkreetse kaupluse sortimenti kuuluvad või mitte.
    • Järgnevad märkmed ainult kirjeldavad, kuidas sortimentide moodul tulevikus tööle hakkab; info võib olla oluline kolmandate osapoolte integratsioonideks.
    • Sortimentides olevatel toodetel on staatus. Tegemist on ühega neljast staatusest, mida saab ka määrata tootekaardil:
      • Aktiivne
      • Ei saa enam lattu tellida
      • Ei ole müügiks
      • Arhiveeritud
    • Tootekaardil olev toote staatus ning sortimentides määratud toote staatus kombineeritakse, et kohaldada laiemat piirangut. Näiteks, kui tootekaardile on märgitud “Ei saa enam lattu tellida”, siis ükski pood ei saa toodet juurde tellida, hoolimata sellest, mis staatus on märgitud konkreetse sortimendi all.
    • Sel moel on endiselt võimalik määrata tootekaardilt tsentraliseeritud piiranguid.
    • Sortimendiga seotud API päringute jaoks palun tutvuge API dokumentatsiooni päringuga “getAssortments”. Veebileht sisaldab viiteid ka teistele sortimendiga seotud API päringutele.
  6. Uus müügikampaania liik

    • Lisatud on uus müügikampaania liik: “Osta vähemalt x tk toodet ja saa kõigilt ostetud toodetelt € / % soodustust”.
      • Näiteks: “Osta 3 (või enam) T-särki ja saa igalt ostetud T-särgilt 2 € soodustust”.

  7. Tootekaardil hinnad kaupluste lõikes

    • Konfiguratsiooni parameetri “show_sales_price_per_store_on_product_card” = 1 abil saab aktiveerida lisabloki (tabeli), milles näidatakse toote hinda kaupluste lõikes (hind km-ga), seejuures kuvatakse nii tavahind kui ka hetkel kehtiv hind. Seda tabelit hakatakse kuvama tootekaardi jaluses.
      • “Tavahind” on enamikel juhtudel tootekaardil olev müügihind. Kui müügihind on tootekaardil (ehk pole defineeritud), siis võetakse hind kauplusele esimesest kehtivast hinnakirjast.
      • “Hetkel kehtiv hind” on reaalne hind, mis kehtib konkreetsel ajahetkel (lõplik hind, mis kujuneb hinnakirjade alusel).
    • USA ja Kanada puhul kuvatakse tabelis netohindu, teiste riikide puhul aga brutohindu.
  8. “Multivaluuta” moodul kassas

    • Tegemist on lisamooduliga, mis võimaldab müüke registreerida mitmes valuutas.
    • Mooduli aktiveerimiseks võtke ühendust klienditoega.
    • Moodul eeldab Berlin POS versiooni 3.25 või uuemat ning klienditoel tuleb aktiveerida konfiguratsiooni parameeter "touchpos_sale_additional_currencies", et defineerida, milliseid valuutasid kassas arvestatakse.
    • Kui moodul on aktiveeritud, ilmub haldurisse “Jaekett” -> “Päeva avamised/lõpetamised” alla uus väli “valuuta”.
  9. Hinnakirja liikide moodul

    • See on ekstra moodul hinnakirjade klassifitseerimiseks.
    • Mooduli aktiveerimiseks võtke ühendust klienditoega.
    • Peale mooduli aktiveerimist tekib hinnakirja loomisel kohustuslik rippmenüü valik “Liik”, mille alt saab valida: “Baashinnakiri” ja “Poe hinnakiri”.
    • Kasutajagrupi õiguste reguleerimise vormile (Seaded -> Kasutajate grupid) tekib valikuvõimalus “Luua ja muuta lisaks “Poe hinnakirjadele” ka teistest liikidest hinnakirju”. Kasutajagrupp, kellel on selle valiku ette märgitud linnuke saab luua ja muuta kõiki hinnakirju.
  10. Actual Reports (kohandatud väljatrükk)

    • Käibemaksumäärade nimetused on lisatud Actual Reports’i müügidokumentide väljatrükile (alajaotustesse “vatTotalsByRate” ja “advancePaymentVatTotalsByRate”) ja ostudokumentide väljatrükile (alajaotusesse “vatTotalsByRate”).
    • Actual Reports’iga trükitud tooteetikettidele on lisatud väljad “basePriceListPrice” ja “basePriceListPriceWithCurrency”. Need kujunevad toote tavahinnast.
      • Väljad “price” ja “priceWithCurrency” näitavad toote hinnakirjajärgset hinda ning väljad  “originalPrice” ja “originalPriceWithCurrency näitavad alati tootekaardil olevat müügihinda.
  11. Teised uued funktsioonid

    • Müügikampaaniatele on lisandunud “Klient saab:” alajaotuses valik “Välja arvatud read, millele on juba rakendunud käsitsi soodustus või mõni muu hinnakirja- või kampaaniasoodustus”.
      • Sellise piirangu seadmine hoiab ära mitmekordse soodustuse rakendumise.
      • Funktsioon vajab “Applied Price Lists” ning “Applied Manual Discounts” ekstra mooduleid. (Samad moodulid, mis aktiveeritakse, et kuvada kassa väljatrükkidel allahindlusi detailsemalt). Mooduli aktiveerimiseks võtke ühendust klienditoega.
    • Lisatud on neljas võimalus viitenumbrite genereerimiseks müügidokumentidel: “Arvepõhine, ettevõtte prefiksiga”.  Selle skeemi järgi saab iga arve unikaalse viitenumbri , kuid samas hakkab tal olema fikseeritud, muutumatu, numbriline prefiks. Selle funktsiooni aktiveerimiseks tuleb minna Seaded → Üldseadistused → Müügidokumentide väljatrükid ja valida “Viitenumber arvetel:” neljas valik avanevast rippmenüüstand.
      • Kui valik on aktiveeritud, tekib ettevõtte kaardile uus väli: Seaded → Minu ettevõtte info → “Arvete viitenumbrite prefiks:”. Selles väljas saate defineerida prefiksi.
    • Tootekaardile on lisandunud linnuke “Kassiir peab kassas hinna sisestama”. Sel juhul peab kassiir alati antud valikuga märgitud toodete hinnad kassas üle kirjutama. Seda funktsiooni toetab Berlin POS versioon 3.26 ja uuemad.
    • Pakkumistes on lisatud tooteridade väljale veerg “Hankija tarnekuupäev”. Siiani on olnud see veerg kasutuses vaid müügitellimuste juures.

LOKALISATSIOON

  • Lisatud on prantsusekeelsed tõlked ning keelevalik. Keele aktiveerimiseks Prantsuse kontodel võtke ühendust klienditoega.
  • Kanada prantsuse keele valik ning tõlked lisatud. Keele aktiveerimiseks Kanada kontodel võtke ühendust klienditoega.
  • Türgi keele valik ning tõlked lisatud. Keele aktiveerimiseks Türgi kontodel võtke ühendust klienditoega.
  • Uuendatud on vene, araabia, läti ja soome keelsed tõlked.
  • Kui Kanada konto pöörata prantsusekeelseks, kuvatakse valuuta sümbol summa järel (“123 $”, varemalt oli “$123”).
  • Klienditoe link on nüüd riigipõhine.

UUED VÕIMALUSED

  • Mõlemaid tootekaardi “Laoaadressi” väljasid (nii rippmenüü kui ka vabateksti) saab nüüd nii eksportida kui ka importida tooteekspordi ja tooteimpordi moodulitega.
  • Väli “Ladu” on lisatud arvelduskäskude vormile. Kui ladu on välja toodud, siis kõik arvelduskäsust koostatud arved hakkavad pärinema eelnevalt märgitud laost.
  • Uus võimalus: müügidokumentide numbreid saab konfigureerida 11-18 pikkuseks.
    • Aktiveerimiseks võtta ühendust klienditoega. Müügidokumentide algusnumbreid saab seadistada nagu ikka Üldseadetes.
    • 8-10 ühiku pikkuseid arvenumbreid hoitakse alati arvetele, mis on tehtud kassas (POS). Seetõttu ei saa neid kasutada back office’is müügidokumentide koostamiseks.
  • Lingid “Vali kõik” ning “Ära vali ühtegi” on lisatud kasutajakaardile ladude valiku juurde.
  • Kasutajate listis ehk üldvaates, kui on kasutajale määratud üle 15 lao, kuvatakse nüüd vaid üldnumbrit (näiteks 15/20 ehk kasutajal on ligipääs 15-le laole 20-st).
  • Frantsiisiketti on nüüd võimalik üles seada selliselt, et peakontol on näha kõikide asukohtade (ladude) laoseise, kuid iga frantsiis näeb ainult enda ladu.
  • “Jaekett” -> “Kauplused” alla on lisatud veerg “Kood” ning filtreerimisvõimalused “Nimetus” ja “Kood”.
  • Lisatud on tugi API päringule “getTaxExemptions” (Tegemist on peamiselt Kanada-põhise aruandlusega seotud featuuriga, mille aktiveerimiseks võtke ühendust klienditoega).
  • Nüüd saab Seaded → Põhjuskoodid all määrata igale põhjuskoodile oma tunnuskoodi. Antud väli võib kasulik olla integratsioonide puhul. Põhjuskoode saab otsida koodide järgi.
  • Põhjuskoodi saab rakendada müügikampaania puhul. Müügikampaania vormil on nüüd ka rippmenüü, mille pealkirjaks on “Põhjuskood”.
    • Peamiselt mõeldud kolmandate osapoolte integratsioonide jaoks.
    • Rippmenüü kuvab ainult neid põhjuseid, mille tüübiks on määratud “Müügikampaania”.
  • Müügikampaaniate ja hinnakirjade nimetusi saab defineerida mitmes keeles.
    • Aktiveerimiseks võtke ühendust klienditoega.
  • Väli “privateNotes” on nüüd saadaval Actual Reports’I müügidokumentide väljatrükkidel.
  • Lisatud on konfiguratsioonisäte: Seaded → Üldseadistused → Klient → “Registrikood / isikukood peab olema unikaalne”
  • Sõltuvalt konto seadetest on aruandegeneraatorisse lisatud väli “Kauba saaja tarneaadress“ või “Maksja aadress”.

PARANDATUD VEAD

  • Parandatud: Kanada kontodel viidatakse maksudele nüüd üldnimetusega “tax” ja mitte “HST”. “HST” on vaid üks maksuliik.
  • Parandatud: Hinnakohased sätted, mis olid reguleeritud konfiguratsiooni parameetriga “invoice_printout_price_decimals” ei töötanud erinevate arve liikide väljatrükil.
  • Parandatud: Kui kinnitamata pakkumise liiki muuta (nt tellimuseks või arveks), siis saab see nüüd uue numbri, kuna pakkumiste numeratsioon erineb tellimuste ja arvete omast.
  • Parandatud: Kui on määratud, et maatrikstoote variatsioon peab saama väljad kood 3, tootja kood, kood 5/6/7 ja/või kood 8 maatriksi ematootelt, siis nende väljade kustutamine ematootelt kustutab ka vastava info kõikidelt tema variatsioonidelt.
  • Parandatud: Polnud võimalik muuta püsikliendipunktide saldot, kui kliendikaardil oli linnukesega määramata “Kasutada POS’i puutetundliku kasutajaliidesega”.
  • Parandatud: Läbi arvelduskäsu komplekttoodet müües ei läinud laost maha komplekti komponendid.
  • Parandatud: Koguselised hinnakirjad rakenduvad nüüd ka negatiivsetele laokogustele. Näiteks kui on määratud, et hinnakiri rakendub kogustele 5 ja enam, siis rakendub sama hind ka tagastuse puhul (kreeditarve).
  • Parandatud: Kliendikaardil kuvatakse nüüd “kodukaupluse” ja “liitus kaupluses” rippmenüüdes “Tundmatu kauplus” kui süsteem ei suuda tuvastada, mis poed antud kliendi all olema peavad. (Puudutab põhiliselt frantsiisikauplusi)
  • Parandatud: QuickBooks ekspordis vastuolu kõrvaldatud.
  • Parandatud: Detailne allahindluste kohane informatsioon läks arve halduris ülesalvestamisel kaduma.
  • Parandatud: Ostuarve või ostutellimuse printimisel läksid kaduma vabatekstina kirjutatud tooted.
  • Parandatud: Kassatšekkide väljatrükil pole enam laekumised ümardatud välismaistesse valuutadesse. (Põhiliselt puudutab Kanada kontosid)
  • Parandatud: Tooteimpordiga ei kirjutata enam KM-määrasid üle (kui impordifailis puuduvad KM-määrad).
  • Hankija hinnakirjast või tavalisest hinnakirjast tootekaarti avades, avatakse see nüüd uues aknas.
  • Parandatud: Kui müügidokument sisaldas põhiliselt vabateksti ridu, siis klienti vahetades mõnikord ei avanenud hüpikaken “Kas soovite hindu uuendada?”.
  • Parandatud: Mitme müügidokumendi väljaprintimisel aeg-ajalt prinditi dokumendid üksteise peale.
  • Parandatud: Ostudokumentide, arvelevõtmisaktide, mahakandmisaktide ja laoliikumiste (üle)salvestamisel ei teki rohkem ebaõnnestumisi, kui toiming võtab aega rohkem kui 30 sekundit. Nüüd on ajalimiit tõstetud 5 minutile.
  • Parandatud: Müügidokumendi kustutamisel eemalduvad nüüd ka seosed teiste dokumentidega.
  • Mõndadel Läti müügiarvete väljatrükkidel olid “Maksja” ja “Kauba saaja” väljad omavahel vahetuses.


ERPLY Back Office versions 4.5.0, 4.5.1

23 October 2017

New features

1. “Store Regions” module

  • This feature allows to group stores into “regions”, and set up price lists that apply to an entire group of stores.
  • Please contact customer support to enable it on your account.
  • Store Regions can be managed in Retail Chain → Store regions. On location form, you can specify which region the store belongs to. Locations can also be filtered by region.
  • A region can be associated with an unlimited number of price lists, and you can change the order in which the price lists will apply. These price lists will apply to all stores in the region.
  • It is also possible to define store region and customer group-specific price lists: price lists that apply only in the specified region, and to customers belonging to the specified group.
  • Price lists will be applied in the following order (and each successive price list overrides a previous one if they contain the same products):
    1. Region price lists;
    2. Region and customer group-specific price lists;
    3. Location price lists.
  • A region cannot be deleted if there is at least one store that belongs to that region.
  • On User form and Employee form, the lists of locations additionally show region name for each location. Similarly, the “Locations and tax rates” block on Product Group form, too, has been augmented with region names.
  • In Inventory → Locations, a new button has been added: “Reorder by Region”. Clicking it will reorder the list of locations by region name, in alphabetical order. (Within each region, the previous ordering of locations will be preserved.) The same rearrangement can just as well be done manually, but on an account with tens of locations, this could be time-consuming.
  • For region-related API calls, see the release notes for API version 1.13.0, or the documentation of API call “getStoreRegions”. This page also contains links to all other related API calls.

2. Restricting promotion to certain regions and/or customer groups

  • This feature allows to specify that a promotion should apply only in certain regions, and/or only to specific customer groups.
  • Please contact customer support to enable it on your account. It also requires the “Store Regions” module that is mentioned above.
  • Enabling the module adds two new fields to promotion form:
    1. [Promotion only takes place] … in these store regions:
    2. Promotion only applies to these customer groups:
  • It is possible to select multiple regions, as well as multiple customer groups.

3. Receipt printout configuration

  • On the Settings → Configuration page, receipt-related settings have been reorganized into a separate section, “Receipt printouts”.
  • Several options which formerly were only editable with a hidden configuration parameter, are now listed:
    • “Redeemed coupons”;
    • “Card payments, detailed” / “Card payments, shortened”. (These two options are not available on US and Canadian accounts: in those countries, the layout of card payment information on receipt is predefined. But these options might be useful in other countries.)
    • “Customer card code”;
    • “Return or discount reason code”;
    • “Attendant’s name”;
    • “Customer’s address”;
    • “Original price”.
  • Additionally, a number of new options have been added. These did not formerly exist at all:
    • Option to remove customer name. (Eg. in case it is desirable to only show the loyalty card number.)
    • “Tax Exempt Number”;
    • “Currency rate for foreign-currency payments”.
    • Additionally, the label for “Total Discount” on receipts can now be set separately for each language.

4. Displaying discounts on receipt

  • Receipts can be configured to display line-by-line detailed information about which discounts were applied to each item. A new group of check boxes in Settings → Configuration → Receipt printouts lets you select which discounts the receipts should show:
    • Promotion discounts;
    • Price list discounts;
    • Manual discounts.
  • For each individual discount, the receipt will display:
    • 1) Discount’s name. This would be the price list name; or promotion name; or manual discount’s reason code, or if there is no reason code, just the text “Manual discount”;
    • 2) How many units the discount applied to; and
    • 3) discount amount per unit.
  • For the “Manual discounts” and “Price list discounts” options to appear, please contact customer support. For either of these options, an extra module needs to be activated on your account.
  • Or, if the option for promotion discounts is not listed, either, there is a module that needs to be activated for that, too.
  • It might be useful to just have the extra modules activated, even if there is no need to have this information on receipt printouts. When the extra modules are activated, cashiers, too, will start seeing the detailed discount information in Berlin POS: all the cumulative discounts and promotions that have been applied to each line.
    • This may, for example, help to track down why POS is offering an item at such a price, or to analyze how a combination of promotions would work in reality.
  • Detailed information of discounts may also be needed in third-party integrations. For retrieving that information over API, please see the documentation of API call “getAppliedPromotionRecords”.

5. “Assortments” module

  • This back office version adds preliminary support for “assortments”, ie. ability to specify different selections of products for different stores.
  • Please contact customer support to enable it on your account.
  • This feature is not functional yet. It is only possible to define the assortments and modify their contents, but they are not being enforced yet. All products can be sold and purchased as usual in POS and in back office, regardless of whether they belong to the particular store’s assortment or not.
  • The following notes only describe how the assortments are going to work; this might be useful information for third-party integrations.
  • In assortments, each product has a status. This is one of the same 4 statuses that can be set on product card:
    • Active
    • No longer ordered
    • Not for sale
    • Archived
  • Product’s status on product card, and product’s status in assortment, will combine to apply the widest possible restriction. For instance, if a product is set as “No longer ordered” on product card, this means that no store will be able to order the item, regardless of what has been set as the product’s status in any particular assortment.
  • This way, it will still be possible to apply centralized restrictions from product card.
  • For assortment-related API calls, see the documentation of API call “getAssortments”. This page also contains links to all other assortment-related API calls.

6. New promotion type

  • New promotion type has been added: “Buy at least x pcs of a product (or from a set of products, or from a product group) and get $ / % off of all those items”.
  • For example: “Buy 3 soups or more and get $2 off each”. If customer buys 3, 4, 5, 6, … soups, all the items (the first three, as well as all subsequent ones) will get the discount.

7. Store prices on product card

  • By setting configuration parameter "show_sales_price_per_store_on_product_card" = 1, an additional block of information can be enabled on product card: a list of stores, and the “Regular Price” and “Current Price” in each store. This might be useful for verifying the combined result of all price lists that have been applied to a store.
    • “Regular Price”, in most cases, will be product card price – or, if product card price is zero (not defined), the price from the store’s first price list.
    • “Current Price” is the actual price that currently applies: when selecting this product in POS (without specifying a customer), this is the price that should be shown on the screen. It is the result of applying all store and region price lists.
  • The table will show net prices in United States and Canada, prices with VAT in other countries.

8. “POS multicurrency” module

  • This is an extra feature which allows to count the register in Berlin POS in multiple currencies.
  • Please contact customer support to enable it on your account.
  • It also requires Berlin POS version 3.25 or newer, and customer support must apply configuration parameter "touchpos_sale_additional_currencies" to define which currencies need to be counted in POS.
  • In back office, when this module has been enabled, field “Currency” will appear on the “Day opening and closing” form.

9. “Price list types” module

  • This is an extra feature for classifying price lists into store price lists and retail chain-wide price lists, and applying different user rights to different types.
  • Please contact customer support to enable it on your account.
  • After this module is enabled, a new, required, drop-down field will appear on price list form: “Type”. The options will be “Base Price List” and “Store Sale Price List”.
  • On user group form, there is a new check box for specifying rights: “Create and edit price lists with other types besides “Store Sale Price List””. Users without that right can only create, edit or delete Store Sale Price Lists. Users WITH that right can create and edit all kinds of price lists.
  • Functionally, there is no other difference between a “Store Sale Price List” and “Base Price List”. (The price lists apply and override each other in the usual manner, regardless of their type.)

10. Actual Reports labels and printouts

  • Tax rate names have been added to Actual Reports sales document printouts (into the "vatTotalsByRate" and "advancePaymentVatTotalsByRate" blocks) and purchase document printouts (into the "vatTotalsByRate" block).
  • On product labels printed with Actual Reports, new fields "basePriceListPrice" and "basePriceListPriceWithCurrency" are available. These contain the product’s “base price”. “Base price” is either product card price – or if product card price is zero, then the price from location’s first price list.
    • In contrast, fields "price" and "priceWithCurrency" show the item’s price as per all price lists that currently apply, and fields "originalPrice" and "originalPriceWithCurrency always show product card price (without the fallback to location’s first price list).

11. Other new features

  • On Canadian accounts, it is now possible to specify “Corresponding GST-exempt tax rate” on tax rate form. For each province’s tax, you need to specify which other tax should apply if GST exemption were activated in POS. This setup will be necessary for using the “Partial Tax Exempt” feature that was introduced in Berlin POS version 3.25.
    • The point is that GST-exempt taxes (First Nations taxes) must be defined in ERPLY as separate tax rates.
    • GST exemption should not affect items that are already tax free anyway, or have only PST. You must define that all these rates get replaced with a First Nations 0% tax.
    • For every other tax rate, you must define that these will get replaced with a First Nations 5% tax.
    • If the option Settings → Configuration → Receipt printouts → Tax Exempt Number has been enabled, the receipts on Canadian accounts will show not only the tax exemption certificate ID, but also the amount of reduced tax.
  • Option “Except lines to which a manual discount or any other price list or promotion discount has already applied” has been added to promotions that give a percentage discount from the whole transaction.
    • Setting this restriction will prevent that promotion for applying double discounts.
    • This feature requires the “Applied Price Lists” and “Applied Manual Discounts” extra modules. (These are the same modules that are needed for showing detailed discounts on receipt printouts.) Please contact customer support to have these modules activated on your account.
  • Fourth option for generating sales document reference numbers: “Invoice-based, with company prefix” — has been added. In this scheme, each invoice gets a unique reference number, but it will also have a fixed, unchanging, numeric prefix. To enable this scheme, go to Settings → Configuration → Sales document printouts and pick the new option from the drop-down field titled “Reference numbers on invoices”.
    • When enabled, a new field will appear on company card: Settings → My company information → “Prefix for invoice reference numbers”. This is where you can define the prefix.
  • Check box “Cashier must enter price in POS” has been added to product card. When selling any of these flagged products via POS, cashier will be required to override the price every time – a corresponding prompt will appear. This feature is supported by Berlin POS version 3.26 and newer.
  • On Quotes, the column “Supplier quoted delivery date” has been added. The same column has formerly been present on Sales Orders.

Localization

  • French language option, and French translation has been added. It can be enabled on French accounts by customer support.
  • Canadian French language option, and Canadian French translation has been added. It can be enabled on Canadian accounts by customer support.
  • Turkish language option, and Turkish translation has been added. It can be enabled on Turkish accounts by customer support.
  • Russian translations have been updated.
  • Arabic translations have been updated.
  • Latvian translations have been updated.
  • Finnish translations have been updated.
  • On Canadian accounts, if user interface is in French, currency symbol will be displayed after the amount (“123 $”, instead of “$123”)
  • The link to Help Center is now country-specific.

Improvements

  • Both “location in warehouse” fields on product card (the drop-down, and the text field) can now be exported and imported with product export and product import modules.
  • Field “Location” has been added to “Recurring billing” form. If you specify the location, all invoices created from that recurring billing will be issued from that location.
  • A new option has been added: sales document numbers can also be configured to be 11…18 digits in length, not only limited to 7 digits and less.
    • Please contact customer support to enable that option. The starting numbers for sales documents can be configured, as usual, from Settings → Configuration → Starting numbers for sales documents.
    • Invoice numbers that are 8…10 digits in length are always reserved for receipts made from POS. This is why these cannot be used for back office sales documents.
  • Links “Select all” and “Select none” have been added to user form, next to the “Locations” heading, to check or uncheck all locations at once.
  • In the Users list, if the list of locations (to which the user has access) is longer than 15, just a total number of locations will be displayed, instead of the name of each. (Eg. “20/25”, meaning that user has access to 20 locations out of 25 total)
  • It is now possible to set up a new franchise chain so that the HQ account will see all locations (warehouses), but each franchisee account will see only its own locations.
  • Column “Code” and filters “Name” and “Code” have been added to Retail Chain → Locations.
  • Support for the “getTaxExemptions” API call has been added. (This is a mostly Canada-specific reporting feature, and needs to be enabled by customer support.)
  • In Settings → Reason Codes, each reason code can now additionally have a “Code”. This would most likely be some alphanumeric identifier, and the field can be useful for third-party integrations. Reasons are searchable by code.
  • It is possible to assign a reason code to a promotion. On promotion form, there is a new drop-down field, titled “Reason code”.
    • This, too, is primarily meant for third-party integrations.
    • The drop-down will only list reasons whose type is “Promotion”.
  • Promotion and price list names can now be specified in multiple languages.
    • If you need this feature, please contact customer support to have it enabled on your account.
  • Field “privateNotes” is now available on Actual Reports sales document printouts.
  • A configuration setting has been added: Settings → Configuration → Customer → “Registry Code / ID Code must be unique”
  • Field “Ship-to address” or “Payer address” on invoices (depending on account setup) has been added to report generator.

Fixes

  • Fixed: On Canadian accounts, tax is now referred to with the generic term “tax”, instead of “HST”. “HST” is just one variation of a sales tax.
  • Fixed: If the price precision on invoice printouts had been customized (using configuration parameter "invoice_printout_price_decimals"), it did not work when printing out multiple documents.
  • Fixed: When an unconfirmed Quote’s type is changed to something else (eg. to a Sales order or an Invoice), it will now also get a new number, because quote numbering is different from the numbering of sales orders or invoices.
  • Fixed: when it has been specified that a matrix variation product should inherit its Code 3, Manufacturer Code, Code 5, Code 6, Code 7, and/or Code 8 fields from the matrix parent, deleting the respective code from the parent will now delete the code from the variations, too.
  • Fixed: it was not possible to change customer reward points amount on Customer form, if the check box “Use POS with touchscreen interface” in Settings → Configuration was unchecked.
  • Fixed: when a bundle product was sold through recurring billing, bundle components were not subtracted from inventory.
  • Fixed: “Quantity price lists” now also apply to negative quantities. For instance, if it has been specified that a price list price applies to quantities 5 and up, the same price will apply when doing a return (credit invoice) for quantity 5 and up.
  • Fixed: on Customer form, the “Home Store” and “Sign-up Store” drop-downs now display “(Unknown store)”, if there is a store assigned to that customer, but cannot be identified. This may be the case in certain franchise setups.
  • One discrepancy fixed in QuickBooks export.
  • Fixed: information about detailed promotions and other discounts that applied to each receipt row was lost when the receipt was re-saved in back office.
  • Fixed: When printing a Purchase Invoice or Purchase Order in a foreign language, “free-text items” did not have a name. The “Product” column was blank.
  • Fixed: on receipt printouts, payments in foreign currencies are no longer converted to receipt currency. For example, on Canadian accounts, a payment of US$200 will be now shown as “Paid (USD): 200.00”, not as “Paid: 248.00” (which was the equivalent value in Canadian dollars).
  • Fixed: importing products no longer resets products VAT rate (in cases where VAT rate is not even being imported).
  • When opening a product card from Supplier Price List or Price List, it will now be opened in a new window.
  • Fixed: when a sales document contained predominantly free-text rows, changing the customer sometimes did not trigger the “Do you want to reload item prices?” dialog.
  • Fixed: When printing out multiple sales documents, they were occasionally printed on top of each other.
  • Fixed: saving or re-saving purchase documents, Inventory Registrations, Inventory Write-Offs and Inventory Transfers will no longer fail if the operation takes more than 30 seconds. (The time limit has been raised to 5 minutes.)
  • Fixed: Deleting a sales document will now also delete links between the deleted document, and any recurring billings and meter readings. (Previously, issues occurred when trying to re-create another invoice from the same recurring billing or reading.)
  • Fixed: on some Latvian sales invoice printouts, the “Payer” and “Recipient” fields appeared switched.


Erply API version 1.17.0

16 October 2017

New features

Assortments

  • New input parameter "getProductsFor" = "SALES" | "ORDERING" has been added to API call getProducts. This filter returns products that the given store is allowed to sell or purchase, according to the store’s assortment. Even if assortments are not in use, it can be used as a status filter.
  • API call getSellableProducts has been added.

Multi-language price lists and promotions

Other

  • Attribute support has been added to API calls getAssortmentsgetStoreRegionssaveAssortment, and saveStoreRegion.
  • Field "cashierMustEnterPrice" has been added to API calls saveProduct and getProducts.
  • Support for “subsidies” (originally added in API version 1.13.0) has been improved; the following fields have been added:
    • "purchasedProductSubsidies" and "awardedProductSubsidies" in API call saveCampaign;
    • "purchasedProducts" → "subsidy" and "awardedProducts" → "subsidy" in API call getCampaigns;
    • "unitItemSubsidy""unitTransactionSubsidy""totalItemSubsidy""totalTransactionSubsidy" in getAppliedPromotionRecords.
  • Configuration parameter "customer_code_unique" = 1 has been added. When enabled, API call saveCustomer will require field "code" (national ID number for persons / registry code for companies) to be unique.

Fixes

  • Fixed: Deleting a sales document will now also delete links between the deleted document, and any recurring billings and meter readings. (Previously, issues occurred when trying to re-create another invoice from the same recurring billing or reading.)
  • Fixed: In API call saveSalesDocument, if a document was re-saved without making changes to document rows, links between the document and recurring billings / meter readings were lost.


Berlin POS version 3.26.0 release notes

21 September 2017

Base version: 3.25.3

New Features

  • Can set customer for offline product prices synchronization via configuration parameter using the customers id
  • Possible to read scanned EAN codes via configuration parameter by using a regex expression designed for the scanned EAN structure
  • Option to enable supervisor PIN validation for manual discounts that exceed the maximum discount limit of the employee

  • Scan customer code, which will select the customer without having focus on the customer field

  • Ability to define document types to be sent to secondary printer for printing via configuration parameter by using a comma separated list of document types
  • Random weighted products supported. These products are bought in to the warehouse by pieces but sold by weight

Improvements

  • Configuration parameter to allow only original tenders on void/return is enabled and the original transaction was completed via gift card then now cash is enabled as a tender for void/return
  • Rounding when using multiple currencies has now been fixed both visually in POS and on transaction documents

Fixes

  • Transaction payment via integration fails then pressing ‘Cancel’ now gives the customer the possibility to do external payment if allowed for integration. If red X (‘cancel’) is pressed instead of external payment and some payments were already covered then they will be voided and customer redirected to payment view (if integration supports voiding previous transactions)


Erply API version 1.16.0

15 September 2017

New features

  • The logic of promotions has been changed: promotions (both invoice-level and item-level promotions) will no longer apply to gift cards.
    • Gift cards are the products that have the “This product is a serial numbered gift card” or “This product is a regular gift card” check box checked on product card.
    • A gift card can still be a promotion trigger (as in “Buy a gift card and get the following discount on some other product”), but it cannot receive any promotion discounts itself.
  • Field "code" has been added to API call getReasonCodes. If you are using Classic back office, version 4.5.0 or newer, you can specify “codes” (alphanumeric identifiers, for example) to Reason Codes. These might be useful for integrations or custom reporting.
  • Field "reasonID" has been added to API calls getCampaigns and saveCampaign – to associate a promotion with a reason code. This might be useful for building custom reports.
  • With API call saveSalesDocument, it is now possible to associate an invoice with a recurring, metered, billing, too — in addition to ordinary recurring billings.
    • Input parameter "billingStatementID#" will accept the ID of a metered billing and will not return an error code.
    • In addition to that, API client must supply input parameter "billingReadingIDs#". For API it is important to know which readings of the meter the invoice must be associated with.
    • If field "billingStatementID#" refers to an ordinary billing, parameter "billingReadingIDs#" must be omitted. Otherwise API will return error code 1013.
  • New API call getTaxExemptions has been added. This is a reporting-related API call.

Improvements

  • API call getChangedDataSince supports querying for 4 new kinds of objects:
    • Inventory Registrations
    • Inventory Transfers
    • Inventory Write-Offs
    • Payments

Fixes

  • Fixed: API call getUserOperationLog did not order the returned records by ID. When retrieving multiple pages of data, API client might not have been able to get the IDs of all deleted objects.
  • Improvements related to record management in franchise chains.
  • Fixed: when adding, updating or deleting an address, the “last changed” timestamp of the related customer or supplier must be updated, too.


ERPLY Berlin Back Office version 5.7.10

29 August 2017

Fixes

  • One discrepancy fixed in QuickBooks export.


Erply API version 1.15.1

29 August 2017
  • Fixes

    • Fixed: promotions with check box “Except lines to which a manual discount or any other price list or promotion discount has already applied” (support for which was added in API 1.14.0) sometimes gave less discount than they were supposed to.
    • Fixed: error in API call getSalesDocuments.


Erply API version 1.15.0

28 August 2017

New features

  • API call getProductStock now allows to retrieve inventory quantity summarized across all locations — by omitting the "warehouseID" input parameter.
    • To exclude the quantities in locations designated as “offline warehouses” for returned inventory, an API client can specify the "excludeOfflineWarehouses" = 1 flag.
    • Please note that it is not possible to simultaneously retrieve total quantity across all locations and:
      • Reorder Points and Restock Levels ("getReorderPoints" = 1);
      • Most recent cost ("getSuggestedPurchasePrice" = 1);
      • Average purchase price and cost ("getAveragePrices" = 1);
      • or, to filter only products with Reorder Point defined or Restock Level defined. To use these filters or flags, "warehouseID" parameter is still required.

Improvements

  • The ability to synchronize changes in reserved quantities with API call getProductStock has been improved.


ERPLY Berlin Back Office version 5.7.9

25 August 2017

Fixes

  • Franchise-related improvements.
  • Fixed: if customer’s home store or sign-up store field is referring to an unknown store, keep the value when re-saving customer card.


Berlin POS version 3.25.3 release notes

21 August 2017

Base version: 3.24.0

New Features

  • Offline login support – Possibility to login to POS and reload it without internet connection (requires configuration setup). Read more about offline

  • Load and store plugins for offline use. POS now supports custom plugins in offline mode as well.
  • Implemented rounding versions in offline mode – document rows tax calculation.
  • Changing language is always available from settings and it’s not linked with user rights anymore.
  • Sale to default customer is allowed in offline mode, even when this is disabled by configuration (as in offline mode default customer is only customer for who sales can be made).
  • Synchronisation of price list prices to offline database daily. This allows to keep prices up-to-date for offline use.
  • Possibility to open and close day with multi-currency.

  • Storing current batch number to EPSI with each payment and close batch button to close day dialog box is added (for Cardlink integration in Greek market).
  • Chase payment provider and integration added (for Canadian market).
  • EPSI public token validation is implemented. Store managers can describe which devices may use POS and which not.

  • New Customer Display Application over EPSI
  • Possibility to change language is always available from settings.
  • Hide customer code on local receipt if configuration “show_customercard_code_on_receipt” is not set
  • Added Vietnamese and Indonesian languages support
  • Two options for tax exempt in POS – partial and full tax exempt (Canadian market)

Improvements

  • Reseting local database is disabled in offline mode.
  • Associate register and on-screen keyboard are available to all users.
  • Init EPSI when user logs to POS in offline mode.
  • External card payment execution is disabled until EPSI sends payment response.
  • When price list module and manual discount usage module is set correct document total discount is displayed.
  • Detecting weight products by regional units.

Fixes

  • Fixed: Incorrect behaviour with split transactions (in Cayan integration).
  • Fixed: When paying with secondary currency, the change amount was not rounded.
  • Fixed: Issues with tax calculation in offline mode.
  • Fixed: Printing in offline got error because of insufficient data regarding warehouse.
  • Payment timeout is changed to 7 minutes (for Cayan integration)
  • Fixed:  Warehouse and register data was not correctly transferred in customer display payload
  • Fixed: PayPal redirect URL (correct clientID)


ERPLY Berlin Back Office version 5.7.7, 5.7.8

17 August 2017

Fixes

  • Fixed: In “Unpaid invoices and balance statements” report, the field “Payments unassociated with invoices” was not displayed in correct currency.
  • Fixed: the Greek fiscal stream line did not contain net totals and VAT totals separated by rate.
  • The time limit allotted to saving or re-saving purchase documents, Inventory Registrations, Inventory Write-Offs and Inventroy Transfers has been raised from 30 seconds to 5 minutes.


Erply API version 1.14.1

16 August 2017

Fixes

  • Fixed: when re-saving a sales document with saveSalesDocument, even when only updating the general properties of the document, “batches” on invoice rows were lost.


Erply API version 1.14.0

14 August 2017

New features

  • “Invoice-level promotions that do not apply on top of other discounts” implemented in API call calculateShoppingCart. If you have classic back office 4.5.0 or newer, you can set up a promotion that gives a percentage discount on the entire purchase, except those items that already have a discount: whether from a promotion, a price list or applied manually by the cashier.
    • To be able to specify such promotions in back office, you also need three additional modules activated on your account: “Promotion Report”“Applied Price Lists” and “Applied Manual Discount”.
  • Support of attributes added for recurring billing — to API calls getBillingStatements and saveBillingStatement.

Fixes

  • Fixed: a promotion “Get $ or % discount on entire purchase in exchange for loyalty points” did not respect the “Further Restrictions” part: that the discount should not apply to certain products, or that the discount should only apply to explicitly listed products.


ERPLY Back Office version 4.4.17 - 4.4.19

3 August 2017

Fixes

  • Fixed: on an invoice printout created with Actual Reports, row quantity was incorrect when configuration parameter "show_package_amount_on_invoice_printout" had been activated.
  • Fixed: for matrix variations added to an invoice, quantity of packages did not get populated.


Erply API version 1.13.0 - 1.13.5

24 July 2017

New features

Price list management

  • For more fine-grained price list management, new API calls have been added to add or remove individual product prices from the price list: addProductToPriceList,editProductInPriceListdeleteProductInPriceList. Also, the product prices in a price list can be fetched page-by-page with new API call getProductsInPriceList.
    • It is still possible to define the whole price list and its contents with the savePriceList API call. The new calls offer just an alternative that may be useful on some occasions — when working with very large price lists, for instance.
  • API call deletePriceList has been added.
  • Filter "pricelistIDs" has been added to API call getPriceLists, for retrieving multiple price lists by ID.
  • The following input parameters have been added to API call getPriceLists, to filter price lists by activity period:
    • startDateFrom
    • startDateTo
    • endDateFrom
    • endDateTo

“Store Regions” module

Regional or customer group-specific promotions

  • This is an extra feature which allows to specify that a promotion applies only in certain regions, and/or only to specific customer groups.
  • Please contact customer support to enable it on your account. It also requires the “Store Regions” module that has been mentioned above.
  • This feature is only available in Classic back office and requires back office version 4.5.0 or newer.
  • This module enables:
    • Filters "storeRegionIDs" and "customerGroupIDs" in API call getCampaigns.
    • Output fields "storeRegions" and "customerGroups" in API call getCampaigns.
    • Input parameters "storeRegionIDs" and "customerGroupIDs" in API call saveCampaign.

Information about applied price list discounts, and applied manual discounts

  • When these extra features are enabled, Berlin POS starts reporting not only which promotions applied to each sale, but also:
    • Which price lists applied, and how much discount each price list gave;
    • How much manual discount was applied. (Manual discount is applied by the cashier in POS by editing price, specifying a discount percentage, or by clicking one of the predefined discount % buttons.)
  • Both of these (applied price lists, and applied manual discounts) are extra modules. Please contact customer support to enable one or both of them on your account.
  • This information does not have a user-visible output (a report) yet, but it can be retrieved with API call getAppliedPromotionRecords. The records returned from getAppliedPromotionRecords will no longer always have a field named "promotionID"; some of the records (those that indicate that a price list discount applied) have a field named "priceListID" instead, and records indicating manual discount will have neither.
  • This feature also requires Classic back office, version 4.5.0 or newer. Also, Berlin POS version 3.25 or newer is highly recommended.
  • With Classic back office version 4.5.0, the applied discounts (promotion, price list and manual discounts) can also be printed on a receipt.

Price list discount shown as discount, on receipt and in printouts

  • Configuration parameter "treat_price_list_discount_as_discount_on_receipt" has been added. With that parameter enabled, sales made from Berlin POS are adjusted so that any discounts from price lists are displayed as discounts. The “-…%” number will include price list discounts, and the “original price”, if it has been enabled, will also show pre-price list price.
    • This only works with online receipts printed from Berlin POS.
    • Additionally, at least the “Promotion Report” and “Applied Price Lists” extra modules must be be enabled (see above), and the “Applied Manual Discounts” module is recommended as well.

“POS multicurrency” module

  • This is an extra feature which allows to count the cash in the register in Berlin POS in multiple currencies.
  • Please contact customer support to enable it on your account.
  • It also requires Berlin POS version 3.25 or newer, and customer support must apply configuration parameter "touchpos_sale_additional_currencies" to define which currencies need to be counted in POS.
  • This feature also requires Classic back office, version 4.5.0 or newer.
  • When the module is enabled, the following extra fields in API can be used:

Package support on documents

  • API calls saveSalesDocumentsavePurchaseDocumentsaveInventoryRegistration, and saveInventoryTransfer now support packages and package quantities for each document row. It is possible to specify, for example, that the item was sold/purchased/received not only in a quantity of 150, but as 15 boxes of 10 pcs. each.
  • Each of these API calls has the following new input parameters (“#” signifies document row number):
    • packageID#
    • amountOfPackages#
  • API calls getSalesDocumentsgetPurchaseDocumentsgetInventoryRegistrations, and getInventoryTransfers output the same information. Each of these API calls has the following new fields for each document row:
    • packageID
    • amountOfPackages
    • amountInPackage
    • packageType
    • packageTypeID
  • Note that package support on Inventory Registrations and Inventory Transfers is not enabled by default. You might need to contact customer support to have it enabled.

Management of “locations in warehouse”

  • For managing the classification of “warehouse locations”, new API calls getLocationsInWarehousesaveLocationInWarehouse, and deleteLocationInWarehouse have been added.
  • Filters "locationInWarehouseIDs" and "locationInWarehouseText" have been added to API call getProducts.
  • Output fields "locationInWarehouseID""locationInWarehouseName" and "locationInWarehouseText" have been added to API call getProducts.
  • Input parameters "locationInWarehouseID" and "locationInWarehouseText" have been added to API call saveProduct.

New promotion type

  • New promotion type has been added: buying a predefined quantity or more of a product, or from a set of products, will reduce the price of all units by a discount amount, or a discount percentage.
  • For example: “Buy 3 soups or more and get $2 off each”. If customer buys 3, 4, 5, 6, … soups, all the items (the first three as well as all subsequent ones) will get the discount.
  • API call calculateShoppingCart will apply this promotion, and fields "percentageOffMatchingItems" and "sumOffMatchingItems" have been added to API calls getCampaignsand saveCampaign.
  • To be able to specify this type of promotion in back office, you need Classic back office version 4.5.0 or newer.

“Assortments” module

  • This API version adds preliminary support for “assortments”, ie. ability to specify different product selections for different stores.
  • This feature is not functional yet; it is only possible to define the assortments and modify their contents, but they are not being enforced yet. All products can be sold and purchased as usual in POS and in back office, regardless of whether they belong to the particular store’s assortment or not.
  • The exact way how assortments are going to work, and what features they are going to provide, has not been fully specified yet.
  • Please contact customer support to enable it on your account.
  • This module enables:

“Price list types” module

  • This is an extra feature for classifying price lists into store price lists and retail chain-wide price lists — and applying more specific user rights.
  • With this extra module activated, users without the right to “Create and edit price lists with other types besides “Store Price List”” are not able to edit, or delete, a price list whose type is not “Store Sale Price List”.
  • Please contact customer support to enable it on your account.
  • This feature is only available in Classic back office and requires back office version 4.5.0 or newer.
  • Installing this module enables:
    • Field "type" in API calls getPriceLists and savePriceList. Please note that when the “Price list types” module gets activated, field “type” becomes a required field in savePriceList. For ERPLY to be able to enforce user rights, it is important that all price lists be classified into categories.
    • Input parameter "types" in API call getPriceLists, to filter price lists by type. This parameter accepts a comma-separated list of type codes.
    • Flag "rightEditRetailChainPriceLists" in API call getUserRights.

“Price list row subsidy and other fields” module

  • This is an extra feature for storing more information attached to a price list row, or a promotion. These additional fields are customer-specific and ERPLY’s standard functionality does not rely on these fields.
  • Please contact customer support to enable it on your account.
  • This feature is only available in Classic back office and requires back office version 4.5.0 or newer.
  • Installing this module enables:

Customer’s “associations” and “professionals”

  • A customer can have two types of related customers: “associations” and “professionals”. This feature, and this terminology, is specific to one customer and ERPLY’s standard functionality does not rely on this information.
  • New API calls saveCustomerAssociationdeleteCustomerAssociationsaveCustomerProfessional, and deleteCustomerProfessional have been added.
  • A list of linked customers can be retrieved with API call getCustomers. Specify input flag getAssociationsAndProfessionals = 1. The returned records will have blocks named associations and professionals.

Dashboard API calls

Other new features

  • API call getConfParameters reports the status of more modules (whether these extra modules are installed or not).
  • New API calls convertPOSLanguageIdentifier and convertAPILanguageIdentifierForPOS have been added. These are used by Berlin POS.
  • It is now possible to set up a new franchise chain so that the HQ account will see all locations (warehouses), but each franchisee account will see only its own locations. This will also require Classic back office version 4.5.0 or newer.
  • New API call getTaxOffices has been added, and field "taxOfficeID" has been added to API calls saveCustomer and getCustomers. This is a Greece-specific feature.
  • New API call getHomeStores has been added. In a franchise, the list of “home stores” or “sign-up stores” may not be the same as the list of account’s own stores. Therefore, when populating a “Home Store” / “Sign-up store” drop-down list with options — regardless of whether it is a franchise account or a regular account — it is recommended to use API call “getHomeStores”, instead of “getWarehouses”.
    • The call will also omit any locations that have been designated as “offline warehouses” for returns.
  • Canada-specific field "gstExemptTaxRateID" has been added to API calls getVatRates and saveVatRate.
  • API call saveSalesDocument can now create invoices that are associated with a recurring billing. The following input fields have been added:
    • billingStatementID#
    • billingStartDate#
    • billingEndDate#
  • The same fields can also be retrieved through getSalesDocuments. The following output fields have been added to each document row: billingStatementIDbillingStartDateand billingEndDate.

Improvements

  • A few improvements have been made to the customer and product search indexes which were added in version 1.12.1.
  • New partner keys have been added.
  • A few deprecated and undocumented calls have been removed.
  • When a location (warehouse) does not have a name in a particular language, API calls getWarehouses and getAllowedWarehouses will return it as-is (an empty string), not the name in English instead.
  • Input parameter "code" has been added to API call getWarehouses, to look up one specific warehouse by its code.
  • Location code can now be modified with API call saveWarehouse.
  • Fields "promotionName" and "priceListName" have been added to API call getAppliedPromotionRecords. These return the name of the price list or promotion that applied to a sale (in addition to the promotion / price list ID, which was already available before).
  • Output field "rowID" has been added to API calls getSalesDocuments (to each invoice row) and getAppliedPromotionRecords. This allows you to map applied promotion discounts and price list discounts to exact invoice rows.
    • Note, however, that row IDs on an invoice change every time an invoice is saved (as a sales document is a versioned object, and on each saving we create a new set of rows in the database), so you should not rely on these IDs when synchronizing data.
  • API calls verifyUserswitchUser, and changePassword now return the endpoint URL and authentication token for “transaction history registry”. These can be found in the "transactionRegistryURLs" block. This is a special integration for one customer. There can be multiple endpoints and tokens configured; if that is the case, API clients must pick one.
  • Fields "addedByUserName" and "lastModifiedByUserName" have been added to API calls getUserRights and getUserGroups.
  • Field "lastModifiedByUserName" has been added to API call getEmployees.
  • API call getUserOperationsLog can be queried for deleted user groups, using input parameter tableName = "userGroups".

Fixes

  • The endpoint and authentication token of customer registry (added in version 1.12.4) are no longer returned as “customerRegistryURL” and “customerRegistryToken”. Instead, in the response of API calls verifyUserswitchUser, and changePassword, there is now a block named "customerRegistryURLs" which can define multiple available endpoints.
  • Fixed: API call getSalesReport returned an empty response when configuration parameter "users_can_see_only_own_warehouse_documents" = 1 had been applied.
  • Fixed: all purchase orders created with savePurchaseDocument were assigned the same number.
  • Fixed: it must not be possible to change the type of a confirmed purchase document with API call savePurchaseDocument.
  • Input parameters "recordsOnPage" and "pageNo" in all API calls are now validated. A non-integer value will return an API error code.
  • Fixed: API call getPriceLists with input parameter "getHeadersOnly" = 1 must still return price list attributes.


Erply API version 1.12.6

10 July 2017

Fixes

  • Fixed: in POS, a promotion gave discount to products, or was triggered by products that had not actually been listed by the user when setting up the promotion.


ERPLY Back Office version 4.4.16

10 July 2017

Fixes

  • Fixed: In “Unpaid invoices and balance statements” report, the field “Payments unassociated with invoices” was not displayed in correct currency.


ERPLY Berlin Back Office version 5.7.5

4 July 2017

New features

  • Feature “Print receipt from payment” has been restored.

Improvements

  • Turkish translations have been added. Turkish language can be enabled on Turkish accounts by customer support.
  • Polish translations have been updated.
  • Russian translations have been updated.
  • Greek translations have been updated.
  • On new Greek accounts:
    • Product units now have Greek translations.
    • Berlin POS is configured to accept cash only for sales totaling 500 € or less, and a Greece-specific POS plugin is applied.
  • On all Greek accounts:
    • On receipt printout, the “Price” columns now shows the price with VAT again. (The change made in version 5.7.2 has been reverted).
    • Improvements in streamline printing on Greek receipts.
  • One reseller branding has been added.

Fixes

  • Fixed: Factoring notice will no longer be shown on waybills, quotes, reservations and orders.
  • Fixed: product import failed if the “Cost” column in the import file contained text “-“.
  • Fixed: If the price precision on invoice printouts had been customized (using configuration parameter "invoice_printout_price_decimals"), it did not work when printing out multiple documents.


ERPLY Back Office version 4.4.15

30 June 2017

Fixes

  • Fixed: In certain occasions, customer list in the sidebar started flickering and jumping around.


Erply API version 1.12.5

7 June 2017

Improvements

Fixes

  • Fixed: when re-saving a purchase document with savePurchaseDocument, the “supplier quoted delivery dates” on document rows were lost.