Checkout Custom Fields for Magento 2

Typical lead time is 5 to 10 business days from when we confirm your field specification and have access to your environment or a copy of your codebase. A simple set of 3 to 5 standard fields lands at the short end; complex conditional logic, file-upload workflows, GraphQL/PWA Studio exposure, or one-step-checkout integration sit at the longer end. We give you a firm date during scoping, build on a branch, and deliver after testing on your staging environment — this is not an instant Marketplace download.

Every build includes 30 days of post-delivery support for defects and configuration tweaks. Because the module is delivered as source under app/code, you own it outright — no per-seat license or recurring fee to keep it running. For Magento minor/security upgrades (e.g., 2.4.7 to 2.4.8), new fields, or feature additions later, we offer an optional maintenance retainer or per-request billing. We pin the build to your current Magento version and document the upgrade path so your team or ours can move it forward safely.

Yes. The module is built on service contracts and extension attributes, so it works on both Magento Open Source and Adobe Commerce on the 2.4.x line. For headless storefronts we expose field values through a GraphQL resolver on placeOrder and the customer order queries, and through the REST V1/orders payload, so your PWA Studio or custom frontend can render, submit, and read the fields. Tell us your stack during scoping and we build the appropriate API surface.

Validation runs in two places. The Knockout UI validates on the storefront for UX, and the values are re-validated server-side inside plugins on the checkout service contracts before they are saved to the quote and order — so a tampered request is rejected. File uploads are constrained by an extension/MIME allowlist and size limit and are stored under a protected media path, not at a guessable public URL. Admin access to view or edit captured values is gated behind a dedicated ACL resource.

Yes — that is a core capability. Each field can be scoped to specific shipping methods (e.g., only for in-store pickup) and/or payment methods (e.g., a PO number only for the Purchase Order method). Fields also support conditional visibility: a field can show or hide based on the value of another field, the customer group, or cart contents. All of this is configured per field in admin, with store-view scope so it can differ across your stores and languages.