Node.js + WordPress/GeoDirectory Developer to Finish Bidirectional Profile Sync

# Node.js + WordPress/GeoDirectory Developer to Finish Bidirectional Profile Sync ## Project overview Haircut Now has a mobile app backed by Node.js, Express, Mongoose, MongoDB, and Amazon S3. Our website uses WordPress, UsersWP, and GeoDirectory. A forward-only, bidirectional profile synchronization system has already been implemented in a draft GitHub pull request. I need an experienced developer to review the implementation, test it against the actual systems, correct any compatibility issues, and safely deploy it after approval. This is not a request to build the integration from scratch. ## Required synchronization For profiles created after this integration is activated: ### Mobile app to WordPress When a new barber completes a profile in the mobile app, the integration should create and link: * A WordPress user * A GeoDirectory barber listing ### WordPress to mobile app When a barber creates a new GeoDirectory listing, the integration should create and link: * A MongoDB app user * A MongoDB shop profile ### Fields synchronized in both directions * Barber name * Phone number * Email address * Structured shop address * Profile photo * Up to two gallery photos Updates to these fields should synchronize in either direction after the accounts are linked. ## Critical forward-only requirement This project must not backfill or automatically link legacy records. Existing MongoDB users, shops, WordPress users, and GeoDirectory listings must remain untouched unless a separate future migration is explicitly authorized. The current implementation includes: * Versioned synchronization markers * Permanent MongoDB and GeoDirectory linkage IDs * HMAC authentication for the WordPress-to-app webhook * Loop prevention for bidirectional updates * Duplicate and out-of-order event protection * Email and phone collision protection * Media-host restrictions for remote image transfers * A custom WordPress plugin * Focused automated tests * Configuration and deployment documentation ## Scope of work The selected developer will: 1. Review the existing draft GitHub pull request. 2. Verify the Node.js, MongoDB, WordPress, and GeoDirectory architecture. 3. Confirm the GeoDirectory REST API field mapping. 4. Confirm the correct format for profile-photo and gallery-photo submissions. 5. Review the custom WordPress plugin hooks. 6. Confirm that the forward-only activation boundary cannot include older records. 7. Configure the required environment variables and WordPress constants securely. 8. Test the following with brand-new test accounts: * App profile creates one WordPress user and one GeoDirectory listing. * GeoDirectory listing creates one MongoDB user and one shop. * Updates synchronize correctly in both directions. * Profile photos synchronize correctly. * No more than two gallery photos synchronize. * Repeated events do not create duplicate accounts, listings, or images. * Existing records remain unsynchronized and unchanged. 9. Correct problems discovered during testing. 10. Add or update automated tests where appropriate. 11. Commit all changes to the existing branch and pull request—never directly to `main`. 12. Provide a clear deployment and rollback checklist. 13. Deploy only after I approve the reviewed pull request. 14. Verify the integration after deployment using new test records. ## Important restrictions * Do not create a backfill script. * Do not modify or automatically link legacy records. * Do not commit passwords, API keys, MongoDB credentials, or other secrets. * Do not push directly to the `main` branch. * Do not deploy without approval. * Do not replace the existing implementation without first documenting why a redesign is required. * Do not make unrelated changes to the mobile apps, website, database, or existing records. ## Required experience Please apply only if you have strong experience with: * Node.js and Express * MongoDB and Mongoose * WordPress plugin development * WordPress REST API * GeoDirectory and its REST API * PHP and WordPress actions/hooks * Amazon S3 image handling * Webhook authentication and idempotency * GitHub branches and pull-request workflows Direct GeoDirectory API experience is strongly preferred. ## Deliverables * Technical review of the existing implementation * Corrections committed to the existing GitHub branch * Passing focused automated tests * Successful testing in both directions with new records * Proof that legacy records remain untouched * Secure configuration instructions * Deployment and rollback checklist * Approved production deployment * Final verification report ## Estimated scope I expect approximately 8–16 hours for a qualified developer because the primary implementation already exists. If you believe the project requires more time, you must first provide specific technical findings and an itemized estimate. Please do not submit a proposal based on rebuilding the entire integration from scratch. Please begin your proposal with the words “Forward Sync” so I know you reviewed the complete job description.