The Plunet vendor portal is the vendor portal for any customer using Plunet. There are hundreds of such vendor portals available in the world, and you can add any number of such portals into BeLazy to watch.

Use cases:

BeLazy supports integration with Plunet vendor portals through a comprehensive connector that enables seamless vendor workflow management. The main use cases where the Plunet integration is valuable:

  • You receive job requests, offers, and direct assignments from Plunet customers and want these managed in your business management system or tracker
  • You want automatic job acceptance and delivery workflows for all vendor selection methods
  • You need to handle first come first served requests, offers requiring approval, and direct assignments
  • You want to deliver projects back automatically when they are completed in your business management system or tracker, or update your system based on manual completion in Plunet

Integration type:

The Plunet integration uses web scraping and logs in with your specific credentials. Due to Plunet's strict enforcement that a user can only be logged in once with the same credentials, you should not log in manually to the vendor portal while the integration is active. If you are logged in manually, BeLazy will retry several times but does not automatically throw an error.

Requirements:

There are no specific requirements to use the Plunet vendor portal. Every Plunet installation's vendor portal can be automated.

 

Expected URL format:

The URL format may vary depending on the Plunet installation, such as https://company.plunet.com or other variations
 

Plunet-specific configuration:

Besides entering your user credentials, the Plunet integration only requires you to configure the decimal number format during connection setup. Select the format that matches your customer's Plunet portal configuration from the available options (e.g., 12345.67, 12.345,67, etc.).


If you do not know the number format but you can ask your customer who has access to admin settings, they can look it up by logging into their Plunet account, selecting Admin from the header, then Settings from the dropdown menu. If they look for Default values for all users they should see the decimal number format next to Separator. If you cannot ask this, log in to the Plunet vendor portal manually and try to look for an invoice or a job that was over a thousand currency units (euros, dollars, etc.), and select the same number format here.


Functionalities and connector-specific information:

  • Unit of acceptance: Job
  • Multiple target languages: Supported through bundling
  • Vendor selection methods: All methods supported - First come, first served (Request), offers requiring approval (Offer), and direct assignment (Assign)
  • Pricing: Extracted from Plunet job information using configured number format
  • Project exclusion: Not supported
  • Download source and reference files: Supported
  • Delivery: Project delivery and file upload supported
  • Manual delivery detection: Supported, delivery date is the date of the first check for delivery detection after delivery
  • Project bundling: Supported
  • 2-factor authentication: Not supported
  • Vendor reassignment: Not supported - Plunet portal does not support this functionality
  • Checklists: Automatically accepted when required
  • Data synchronization: All information that appears in the Plunet vendor portal appears in BeLazy
  • Project manager information: Email addresses are not extracted because they are not visible in the Plunet portal


Typical issues and how to resolve them:

  • Job closing permissions: In rare cases, you may be able to upload files but not close the job. BeLazy will not notify you of this issue, and you would not be able to close the job manually in the vendor portal either. To resolve this, ask your customer to enable delivery permissions under Admin / Settings / Jobs in Plunet, in the Job delivery possible by following roles section, by enabling the checkbox next to Assignee
  • Project bundling and workflow structure: Each workflow in Plunet is single-step. You can use the job bundling to turn consecutive steps such as translation, revision into one workflow in your business management system or tracker. For tasks like LQA or LSO for the same project, we recommend using task bundling, meaning they are added under the same project in Plunet, XTRF Classic and any custom integration under a new task or item. Daily and monthly project bundling and project bundling creating one project with different language pairs are supported.
  • Instruction mapping: All instructions are extracted from the various instruction fields in Plunet, and can be automatically reused in your customizable, client and program-specific instructions to the project managers and the vendors.
  • Synchronization: By default, the connector is synchronized every 30 minutes, but you can also synchronize immediately once an email with a new job offer comes in.


Connector-specific data extracted: See here.