Tel: +44 208 776 5979 | Fax: +44 208 659 5984

Focus Advanced Publishing software ™

continues to evolve based on customer requests and
the overall direction the book industry

FAP is GDPR Compliant

The EU General Data Protection Regulation (GDPR) approved by the EU Parliament on 14 April 2016, goes into effect 25 May 2018.

It applies to all companies processing and holding the personal data of data subjects residing in the European Union, regardless of the company’s location.

The Focus GDPR implementation supports the principle of “Privacy by Design”, that is, straight out-of-the-box.

Focus understands that its products and services will form part of the controls and processes that businesses will implement in order to meet some of their own GDPR obligations.

Here are the main GDPR changes to expect in the system FAP version 7.43 or later:

Customer window
  • we now track every access or lookup of a customer record, even if you did not make or save any changes.
  • when you save a record, we now write a detailed changes log to meet the GDPR requirement.
  • clicking the delete button, in order to meet the “Data subject access requests”, Focus will apply stringent rules, as explained later under the “Right to erasure"
Marketing Window
  • all exports to email, label, Excel or printer are tracked to meet the GDPR requirement.




Editorial and Production Module
Profit and Loss by Project Report

Profit and Loss by Project Report has been introduced into the Editorial and Production Module, and it is located at the top-left of the window.

The report presents an instant profit and loss Report for all product types and it shows the following columns per product type: Price, quantity, sales value, expenses, contribution and the Return on investment (ROI).

The report may be viewed on the screen, emailed, or output to Printer, Excel, PDF or CSV, as shown.


Product Sales Analysis

The “Sales Analysis” feature in the Product Window just got better. First introduced in the older system, Focus on Publishing Software, to enable users to perform a quick analysis of a single title, it was loved by users but was plagued by speed problems and often buckled under memory demand.

However, with better memory handling in Focus Advanced Publishing software, we have reintroduced “Sales Analysis” into the Product Window, by popular demand. Not only can users perform analysis of sales of a single title faster, they have 10 different analysis types to choose from.

It is all the more easily accessible, just go to ‘Accounts > Product’, select a product code and click ‘Sales Analysis’.

Available analyses include: By

  • Customer
  • Financial Year
  • Financial Year/Period
  • Geographical Area
  • Account Type
  • Sales Type
  • Country
  • Campaign
  • Location
  • Nominal Code

Make AI Sheet More Responsive

The title data, publisher’s logo, style and imprint brought together on the typical Advanced Information (AI) sheet can be both instant and responsive.

You are now able to print, email, PDF or preview an AI Sheet of the title that is currently shown in the Product window, using the underlying default AI template.

The default AI template is designed to be responsive, as, if required in a multi-imprint and -publisher mode, it can automatically switch logo and style, depending on the title, imprint or publisher

Where you use different AI template per imprint, Focus Support can help bring these AI Templates into a single, but multi-layered template, which will respond to the value stored in the AI Template field, and will dynamically choose the required AI Page in the default AI Template.


Royalty Module features NEW royalty type

To help meet the demands of the most challenging author contracts, especially in trade publishing, we have introduced a NEW royalty type called “Discount Range”.

It allows the user to specify the applicable royalty rate by discount range, and depending on the accumulated-quantity-sold and where it fits in the defined Quantity-sold ranges per geographic region.

After specifying the escalated discount and the quantity-sold ranges per geographic region, the system also presents the user a choice of 2 royalty-calculation methods: by (1) Net Receipt or (2) Published Price.

Note: Generally, in trade-publishing, Local Sales are usually based on published price/RRP, whereas Export Sales are based on Net Receipt.

If you are interested, please contact your software vendor or email info@focusservices.co.uk for more information.

In the image below: (1) Discount range columns, (2) Quantity sold range columns (3) Royalty-calculation Methods: (net receipt or RRP).


Figure 1: Royalty Module


Figure 2:
Sample royalty statement
Royalty Module


Editorial and Production Module

The Target publication date can now be auto-projected from the selected “Type of Schedule”, which has been pre-set to choose “Revised Manuscript Date” or “Handover Date” as the project starting date, plus the total duration from the selected “Schedule Template”. The Target publication date suggested by the system may be manually overwritten, for example, if a specific day of the week was preferred.

The “Type of Schedule” is pre-set, in our preferences, to choose “Revised Manuscript Date” or “Handover Date”, as the starting date in all its uses.

The “Schedule Templates” contains the individual tasks and their duration that make-up the project-cycle.

Figure 1: Editorial and Production Module


Figure 2: Editorial and Production Module



Auto-emailed Customer Statements / Chase Letter

When customer statements are auto-emailed, the system by default suppresses customer statements with the negative balances. This has been the case for over 18 years, as publishers did not wish to alert customers of credit balances held on their behalf.

We have introduced a criteria system that allows each user-client to specify the criteria to be applied in the auto-customer statement releases as shown below.
Figure 1: Auto-emailed Customer Statements / Chase Letter


ONIX

We have introduced a “text only” blurb feature across all blurb types, in Editorial and Production module and Product Window, to help customers struggling to keep within the 300 character limit set for short blurbs.

Note: When exporting blurb fields into a standard ONIX file (XML format); we are forced to include extra escaping commands around the XHTML coding, otherwise the ONIX file will fail. These extra coding may inadvertently extend the blurb beyond the 300 character limit.
Figure 1: ONIX