External Vendor Integrations (Welocalize / Junction / Moravia) — business view

1. Business Summary

Polls partner platforms for inbound work offers/jobs, maps fields (language, unit, task type), accepts work, and creates internal Tasks/Jobs/RFRs.

2. Business Value

Automated work intake from larger LSP partners — major revenue stream.

3. Users / Stakeholders

Vendor managers, operations, finance.

4. Workflows

• Polling jobs run per account/brand on a schedule.
• A limiter filters offers by available languages and word-count caps.
• Bulk acceptance endpoints assert work back to the partner.

5. Sub-Features

• Token/credential management per partner.
• Language/task-type mapping templates.
• Acceptance tracking and logs.

6. Business Rules

• Limiters filter by language and word limits.
• Partners require certifications for some languages (Junction).
• Some flows accept offers in bulk.

7. Data Entities

Welocalize Offers / Languages / Account Token / Task / Log; Junction Task; Moravia Job.

8. Entry Points

• Partner integration screens; cron jobs per account/brand.

9. Inputs & Outputs

• Inputs: external offers.
• Outputs: internal Tasks/Jobs/RFRs.

10. Integrations

• Welocalize, Junction, Moravia partner APIs.

11. Calculations / Logic

• Field mapping and limiting.

12. Status Lifecycle

• Offer → accepted → assigned → completed.

13. Permissions

• Vendor management; brand-scoped.

14. Reports & KPIs

• Offer counts, acceptance rate, throughput per partner.

15. Risks & Observations

• Hard-coded tokens / JWTs in code.
• Fire-and-forget acceptance — failures may not be retried.
• No rate limiting on inbound API.

16. Source Code Evidence

• app/Controller/{WelocalizeController, JunctionController, MoraviaController}.php.