The customer selection step always appears, but what you need to choose depends on the system you are connected to.
Plunet: Select the customer from the list. The list also shows the customer’s preferred currency. Plunet automatically applies the price list based on its configuration.
XTRF (Classic and Smart projects): You need to select both the customer and the price profile. This allows you to apply different prices for different project types.
Protemos: Select the customer and the CAT log scheme. Pricing depends on additional details like specialization.
REST API: Only the customer is selected. Handling pricing variations is up to the developer.
In BeLazy, some projects come with a predefined price, others do not. If the price is provided by your customer or system, BeLazy imports it directly. If not, your business management system needs to determine the price using the correct price lists or rules.
When working with translation management systems such as Phrase or memoQ, you may receive projects from multiple customers. In these cases, you can use metadata (such as Buyer, Customer, or Client) to assign the right customer.
A more complex case is Welocalize Junction, where jobs can come in different currencies and from multiple offices. Here, it is best to create exceptions based on both currency and office, and ensure all customers are properly set up in your business management system before configuring BeLazy.
Tip: If you are using Plunet, and after the initial configuration the system does not select the right price list, consider that it is not exclusively the customer selection that defines the price list: the workflow-based rate mapping and the order template selection both Plunet’s price list selection logic. For the receivables, only map units that are in the price list you wish to assign for projects, and use the order template to set up the order metadata that the price list matches with.