Official communication channels
The contact form is the primary enquiry route. Phone contact details are listed in the footer for urgent channel clarity.
Contact eComHut about Magento, Adobe Commerce, Drupal, ecommerce integrations, technical SEO, support, upgrades or web development requirements.
The contact form is the primary enquiry route. Phone contact details are listed in the footer for urgent channel clarity.
Share the website URL, platform, main outcome, problem timeline, third-party systems involved and ecommerce details where relevant.
A good first message explains whether the work is exploratory, urgent, launch-related or part of ongoing improvement.
Contact eComHut when you need help with a live ecommerce platform, a planned Magento or Drupal project, an integration, an upgrade, technical SEO, performance or a business website. The fastest route to a useful first response is to explain the platform, affected journey, business impact and desired outcome rather than trying to choose the perfect internal service label.
For development work, include the store version, important extensions, theme/storefront approach and integrations where known. For production issues, explain whether orders, payments, shipping, customer accounts, admin users or catalogue updates are affected. For upgrades, include the current Magento/Adobe Commerce version and the target or support concern that is driving the project.
Useful starting points include Magento development, Magento support and maintenance, Magento upgrades and migrations and Magento consulting.
For Drupal, include the current version, content/editor pain points, module concerns and whether the goal is support, upgrade, migration or restructuring. For ecommerce integrations, describe the source system, destination system, data being moved, processing frequency and how failures are handled today. For a business website, explain the audiences, services, CMS needs and the actions visitors should take.
If a live store is down or revenue is actively affected, lead with the business impact. State when the incident started, which users are affected, any recent release or infrastructure change, and whether admin access, checkout, payment, order creation, search or catalogue updates still work. That makes triage materially faster than a message that only says the site is broken.
Do not send passwords, private keys, payment credentials, API secrets, customer records or full database exports through the public form. Send a sanitized summary first. If private access or commercial information is required, agree the appropriate confidentiality and access process before sharing sensitive material.
The request is reviewed to determine whether it needs support, focused investigation, consultation, technical audit or defined implementation. If important information is missing, the next response should ask for the smallest set of details needed to move forward rather than forcing a long generic discovery exercise.
Yes. Include the store URL, edition/version, affected functionality, integrations and expected result so the scope can be reviewed responsibly.
Yes. Existing Magento, Adobe Commerce, Drupal and other web platforms can be investigated and improved without assuming a rebuild.
No. Send enough context to qualify the requirement first, then agree a safe access method if private system review is needed.