
Magento API Cart Issue + 8 UX Fixes – Developer Required
- or -
Post a project like this33
$30/hr
- Posted:
- Proposals: 12
- Remote
- #4449999
- Awarded
⭐ TOP RATED - UK Based AI Developer|Designer|E-Commerce|Content Writer|Social Media Expert|2D/3D Animator


UK's Most Trusted Full-Stack Mobile App & Software Developer | Expert Cloud Architect, AI Automation Specialist & Web Solutions Provider

PPH #1 "Top Rated" Service Provider in Development & IT : Wordpress, Shopify, Magento, Squarespace, ZOHO, WHMCS, Salesforce, Vtiger, Learndash, Moodle

Data Science & Machine Learning Engineer | Web App developer | AI Application Development
TOP Rated Shopify, ROR, Drupal, Magento, PHP, iOS, Android developer

277433411972778775393210548737253732312308590241816129015991166743742964818405958874984
Description
Experience Level: Expert
We are looking for a Magento 2 backend developer who can fix one remaining API issue and resolve eight small UX issues on a Magento 2.4.3-p3 store.
============================================================
WHAT HAS BEEN DONE
============================================================
• Full checkout API flow (cart → shipping → payment → order) has already worked twice.
• Stripe 3.5.x modules removed, replaced with Webkul mpstripe (working).
• Two successful Payment Intent orders prove the checkout pipeline is stable.
• Postman still works for cart creation; cURL does not.
• The ONLY backend issue left:
→ Creating a fresh logged-in customer cart via API using cURL returns a customer object instead of a quote ID.
• Logs confirm: NOT a module issue, NOT a configuration issue, NOT a data issue.
• This is purely a REST request-format or context mismatch.
============================================================
WHAT THE DEVELOPER MUST DO (API)
============================================================
1. Make cURL match Postman EXACTLY
- Same headers
- Same body format (empty JSON handling)
- Same cookies + PHPSESSID
- Same store/website scope
2. Identify why Magento returns a customer object instead of a cart.
- Investigate request interpretation
- Fix context/scope/session mismatch
3. Restore consistent API flow:
- Create cart
- Add items
- Estimate shipping
- Set shipping-information
- Place order (already working)
============================================================
WHAT THE DEVELOPER MUST DO (UX ISSUES)
============================================================
There are **eight small UX issues** on the frontend that must be fixed. These include:
• Minor layout inconsistencies
• Button/CTA alignment issues
• Two styling fix requests
• One text/label correction
• One mobile display issue
• One form validation glitch
• One simple checkout-step UI adjustment
(Exact list will be provided - each is small and quick.)
============================================================
REQUIREMENTS
============================================================
• Strong Magento 2.4 backend/API experience
• Strong understanding of REST statefulness, QuoteRepository, and sessions
• Ability to debug requests, headers, cookies, Varnish/Nginx behaviour
• Ability to fix frontend UX issues (HTML/CSS/JS/Magento layout)
• Work efficiently and avoid unnecessary module disabling
============================================================
SUMMARY
============================================================
Backend is healthy. Stripe works. Checkout works.
We only need:
✔ Fix the API cart-creation context issue
✔ Fix eight small UX issues
✔ Deliver a stable, reproducible checkout API flow and a clean user experience.
============================================================
WHAT HAS BEEN DONE
============================================================
• Full checkout API flow (cart → shipping → payment → order) has already worked twice.
• Stripe 3.5.x modules removed, replaced with Webkul mpstripe (working).
• Two successful Payment Intent orders prove the checkout pipeline is stable.
• Postman still works for cart creation; cURL does not.
• The ONLY backend issue left:
→ Creating a fresh logged-in customer cart via API using cURL returns a customer object instead of a quote ID.
• Logs confirm: NOT a module issue, NOT a configuration issue, NOT a data issue.
• This is purely a REST request-format or context mismatch.
============================================================
WHAT THE DEVELOPER MUST DO (API)
============================================================
1. Make cURL match Postman EXACTLY
- Same headers
- Same body format (empty JSON handling)
- Same cookies + PHPSESSID
- Same store/website scope
2. Identify why Magento returns a customer object instead of a cart.
- Investigate request interpretation
- Fix context/scope/session mismatch
3. Restore consistent API flow:
- Create cart
- Add items
- Estimate shipping
- Set shipping-information
- Place order (already working)
============================================================
WHAT THE DEVELOPER MUST DO (UX ISSUES)
============================================================
There are **eight small UX issues** on the frontend that must be fixed. These include:
• Minor layout inconsistencies
• Button/CTA alignment issues
• Two styling fix requests
• One text/label correction
• One mobile display issue
• One form validation glitch
• One simple checkout-step UI adjustment
(Exact list will be provided - each is small and quick.)
============================================================
REQUIREMENTS
============================================================
• Strong Magento 2.4 backend/API experience
• Strong understanding of REST statefulness, QuoteRepository, and sessions
• Ability to debug requests, headers, cookies, Varnish/Nginx behaviour
• Ability to fix frontend UX issues (HTML/CSS/JS/Magento layout)
• Work efficiently and avoid unnecessary module disabling
============================================================
SUMMARY
============================================================
Backend is healthy. Stripe works. Checkout works.
We only need:
✔ Fix the API cart-creation context issue
✔ Fix eight small UX issues
✔ Deliver a stable, reproducible checkout API flow and a clean user experience.
Projects Completed
39
Freelancers worked with
35
Projects awarded
48%
Last project
6 Dec 2025
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies