Revive Ecwid-Moodle-Keplero Automation Flows

After a recent server reconfiguration and full migration to a new shared hosting environment, our Ecwid–Moodle–Keplero automation flows stopped working.

Before the migration, the system was fully automated and stable.
At the moment, users are being activated manually and reminder emails are sent by hand, which is not sustainable.

We are looking for a senior, reliable developer who can restore and adapt the existing automation to the new server stack and make it fully operational again.

This is not a greenfield project:
the overall logic already exists, part of the custom scripts and plugins are still present, but they need to be refactored, completed, and tested end-to-end.

-Core Automation Logic

The system must handle the following flows automatically:

1. Purchase → Course Access

When a customer purchases a course via Ecwid:

A Moodle account must be created or updated

The user must be enrolled in the correct Moodle course

Start and end dates must be automatically applied via Keplero

2. Expiration & Renewal Logic

5 days before course expiration, the student must receive a renewal reminder email

Additional “booster” logic should push eligible users toward the OPEN plan, when applicable

3. Course Suspension & Reactivation

Temporary course suspensions (from 1 to 3 weeks, depending on the plan) must:

Automatically suspend access

Automatically restore access on the correct restart date

-Existing System Notes

This automation worked correctly before the server migration

Part of the custom logic and scripts still exist

There are custom plugins/hooks running on both Ecwid and Moodle

These hooks must remain intact during refactoring

The task is to adapt and complete the logic for the new hosting/server environment, not to redesign everything from scratch

-Additional Requirement

In addition to restoring the existing automation, the developer must also:

Set up the same automation logic for two new courses

Ensure the system is scalable and easily extendable for future courses

Deliverables

-Fully functional automation running on the new server

-Live testing with a small group of real users to validate every flow

-Short, clear technical documentation so another developer can maintain or extend the system in the future

The goal is to return to zero manual administration.

Developer Profile Required

We are looking for someone who:

Has strong experience with Moodle, Ecwid, APIs, and server-side automation

Is senior-level, precise, and reliable

Can work independently without constant supervision

Understands the importance of testing and clean handover documentation

Budget note: This is a production-level system, not an experimental task.
The scope and value of the work are clearly defined.
The budget will be aligned with concrete delivery and results, not with generic seniority claims.
Only developers able to execute independently, on time, and without trial-and-error should apply.