OpenCart answers, already organised

ALTER TABLE `table_name` CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;

ALTER TABLE `table_name` ENGINE=InnoDB;

ALTER TABLE `table_name` ENGINE=MyISAM;

A full OpenCart backup needs a database copy and all site files, including images, downloads, config files, and custom changes.

Use the OpenCart backup guide before upgrades, hosting moves, or extension changes.

Backup frequency depends on how often orders, products, and customers change. Daily backup fits active e-shops, and a manual backup is always needed before upgrades or major changes.

Backups should also be stored outside the main server.

On stores with large product catalogs, search can become slow because of queries, indexes, filters, or custom theme code. A practical option is Qwik.Select, which provides fast product search with fuzzy search, autocomplete, filters, categories, and Greeklish support.

If your site needs tailored search optimization, we can build custom code that makes search faster for your exact catalog and theme. See the quote page. A live quote request requires login, so open a new protected quote.

This means that one or more of the following occurred:

• you installed our company's software without a valid license.
• you resold our company's software without a valid license.
• you communicated with our company in a way that was not appropriate for professional communication.
• you sent multiple spam messages to our company.
• your account was reported by a legal authority.
• your account was reported by other users (you received an abuse warning 10 days before the account was blocked).
• you did not pay outstanding invoices within the agreed time frame.

Unfortunately, account blocking is permanent and the status cannot be changed. Any other profiles using the same contact details, payment details, or domain(s) may also be blocked immediately upon activation.

The ACS Courier plugin supports ACS API cost, fixed cost, percentage adjustment, and fixed amount adjustment per ACS option, with priority rules and automatic currency conversion.

Yes. The ACS Courier plugin supports checkout visibility rules for products, categories, manufacturers, or all carts. Exclude rules always win over include rules.

Yes. In the ACS Courier plugin, a fixed fee can appear before point selection, but ACS Store or Locker selection is still required for correct shipment creation.

The Box Now Lockers plugin adds locker selection to checkout, stores the pickup point on the order, and helps create the voucher and label from admin.

Before going live, check shipping cost, regions, and compatibility with your checkout theme.

The Courier Center plugin brings voucher creation, cancellation, printing, and tracking into OpenCart.

It is useful when your team wants less manual entry and a cleaner shipment history on each order.

Yes. With the ELTA Courier plugin you can create vouchers, store shipment details, and follow order shipment progress from OpenCart.

Account settings and order statuses should be configured before daily use.

Yes. The Speedex Courier plugin for OpenCart supports daily shipping workflows such as voucher creation, tracking, and shipment data management from admin.

Before production use, check partner credentials, order statuses, and checkout compatibility.

Yes. The Geniki Taxydromiki plugin for OpenCart helps with voucher creation, shipment tracking, and reduced manual entry.

Correct setup depends on your courier contract, the services you use, and the order statuses you want to update.

To enable ACS Courier vouchers in OpenCart, you need ACS Web Services credentials, a compatible shipping extension, and a test voucher flow using a real order.

If you want a ready-made option without custom development, see the ACS Courier plugin for OpenCart with voucher creation, tracking, checkout rules, and the full version at €39.99 with lifetime updates.

The ACS Courier plugin for OpenCart is available as a full version at €39.99 with lifetime updates. The price covers the extension itself; installation, ACS Web Services configuration, or special checkout rules can be scoped separately.

Review the feature set on the ACS Courier plugin page before deciding whether you need only the license or also technical setup support.

Automatic voucher creation reduces manual copying, speeds up order shipping, and keeps tracking inside the OpenCart workflow. It becomes useful when order volume grows or the team needs a stable label-printing process.

For Greek courier operations, start from the courier plugins for OpenCart and choose the integration that matches your courier contract.

Pickup points and lockers need a checkout flow where the customer can choose a location, the selected point is stored on the order, and the right data is sent to the courier.

Depending on the provider, you can review options such as ACS Store / Locker or Box Now Lockers for OpenCart.

Different courier options per cart usually depend on products, categories, manufacturers, weight, delivery region, or payment method. This helps hide unavailable methods and apply the right shipping cost.

The ACS Courier plugin for OpenCart supports pricing and visibility rules for ACS checkout options without database changes.

A Skroutz XML feed is used to send products, prices, and availability to the marketplace. Skroutz Smart Cart is about the order workflow that comes from Skroutz and requires a separate connection.

For feeds, see CSL Skroutz Feed Pro. For marketplace orders, see Skroutz Smart Cart for OpenCart.

You need an OpenCart connection with Wolt or efood when you want to reduce duplicate entry for products, prices, availability, or orders between the e-shop and the marketplace.

A reliable implementation starts with field mapping and test orders. See the pages for Wolt Integration and efood.gr Connector for OpenCart.

An OpenCart connection with SoftOne ERP is useful when products, orders, customers, prices, or stock need to sync without manual exports and imports.

Before implementation, define fields, sync direction, cron jobs, and error handling. See the SoftOne Connector for OpenCart for the core workflow.

OpenCart needs a custom integration when there is no ready-made extension for the ERP, marketplace, courier, warehouse, or third-party API you use, or when your business rules are more complex than a standard installation.

In that case, start with technical scope, data mapping, and a test environment. See custom OpenCart integrations.

Manual work is reduced with automation for orders, stock, ERP, marketplaces, courier vouchers, status updates, and error checks. The best starting point is the stable process your team repeats most often.

For larger workflows, see enterprise automation for OpenCart.

If OpenCart stops accepting orders, capture the exact error, note when it started, check recent payment or extension changes, and avoid repeated live changes without a backup.

For faster diagnosis, open a request through the support questionnaire or review the OpenCart technical support plans.

Before an OpenCart upgrade, check the PHP version, theme, OCMOD/VQMOD changes, custom code, extensions, payments, shipping methods, and backups. The upgrade should be tested in staging before production.

For a structured process, see the OpenCart upgrade service.

You need professional optimization when categories, search, checkout, or admin are slow, when hosting appears overloaded, or when basic cache changes do not solve the issue.

Proper diagnosis looks at database queries, extensions, theme code, images, cache, and server resources. See the OpenCart performance optimization service.

A security audit is needed after suspicious activity, unknown files, spam orders, strange redirects, old PHP or OpenCart versions, or before a high-sales period.

The review covers files, admin access, extensions, permissions, logs, and practical hardening steps. See the OpenCart security audit service.

Managed hosting is worth it when the store needs server monitoring, backups, infrastructure updates, performance work, and support that understands OpenCart operations.

If you often face downtime, a slow admin, or unclear responsibility between host and developer, review the managed hosting services.

Yes. We can build an OpenCart e-shop from scratch with catalog structure, checkout, payments, shipping, SEO foundations, speed work, and admin handover.

For project requirements and next steps, see the OpenCart eShop development service.

OpenCart eShop development cost depends on product volume, design, payments, shipping carriers, ERP, marketplace connections, data migration, and SEO requirements. There is no reliable fixed price without technical mapping.

For an initial estimate, review the OpenCart eShop development service and send the key project requirements.

OpenCart eShop development time depends on project requirements, product and content readiness, integrations, and checkout testing. A proper project moves through technical mapping, implementation, testing, revisions, training, and go-live.

A more accurate timeline needs a short project mapping step.

Yes. A new OpenCart eShop can connect with payment gateways, shipping carriers, ERP, marketplaces, or custom APIs when fields, rules, order updates, and tests are defined early.

For a project starting from scratch, include these integrations in the project requirements for OpenCart eShop development.

You need a custom OpenCart extension when a feature must be reusable, maintainable, and separate from fragile core or theme edits. It is usually the better path for integrations, checkout rules, admin tools, and commercial workflows.

See the custom OpenCart extension development service to start with a clear scope.

Yes. OpenCart can support a B2B or wholesale store when customer groups, price lists, access restrictions, minimum quantities, and the order flow are planned correctly.

For a serious B2B project, the structure should be designed before importing products or starting ERP integration, so the store can support retail, wholesale, or a mixed model without fragile exceptions.

An OpenCart B2B eShop needs clear customer groups, prices per partner or category, new-account approval, VAT rules, minimum quantities, fast reorder flows, and correct ERP integration where an ERP exists.

If the wholesale flow has special rules, a custom OpenCart extension may be safer than a simple theme configuration or off-the-shelf module.

Yes. An eShop can be migrated to OpenCart from another platform, as long as data quality, product structure, images, customers, orders, and old SEO URLs are reviewed first.

The migration should happen in a staging environment and be completed with checkout tests, redirects, and technical checks before the live domain changes.

An OpenCart migration usually includes products, categories, images, manufacturers, customers, orders, core SEO fields, and old URLs that need 301 redirects.

Not every dataset transfers cleanly with one export. Before migration starts, field mapping, duplicate checks, and an SEO protection plan are needed. See also the FAQ on SEO migration to OpenCart.

Yes. An OpenCart store can sell in Greece and Cyprus, but countries, geo zones, VAT, currencies where needed, shipping, payments, and checkout messages must be configured correctly.

For commercial operation in both markets, define shipping rules, payment methods, and SEO content for Greece and Cyprus early, instead of adding isolated fixes after launch.

Cyprus shipping in OpenCart needs correct geo zones, cost rules by weight or cart value, clear delivery-time messaging, and a check that the courier or shipping plugin supports the required workflow.

If you have your own courier agreement, the commercial rules should be reflected in checkout and voucher creation should be tested before the store goes live.

Yes. OpenCart can connect with JCC or another Cyprus payment gateway when there is a compatible payment extension or a custom integration with correct redirect, callback, and order-status handling.

Before implementation starts, confirm the OpenCart version, the bank or provider technical details, test transactions, and how the store will handle failed or cancelled payments.

Before adding a Cyprus payment gateway to OpenCart, check version compatibility, SSL, callback URLs, order statuses, test cards, currency, checkout language, order emails, and payment logs.

The integration should not be judged only by whether the payment page opens. Test successful payment, failure, cancellation, bank return, and order update inside the admin.

An OpenCart store with thousands of products needs a clean category structure, useful filters, optimized images, database indexes, fast search, careful feeds, and hosting that can handle admin work, imports, and checkout.

Before the catalog grows, review imports, attributes, manufacturers, and SEO URLs because catalog mistakes become much more expensive once they are published at scale.

OpenCart search and filters improve with clean product data, correct attributes, fast database queries, indexes, cache where safe, and a UI that helps customers narrow results quickly.

If the store has a large catalog or special commercial logic, it may need custom search, database optimization, or a dedicated extension instead of a simple template change.

Improving an OpenCart store is usually better than rebuilding when the core store works, the data is clean, and the main issues are speed, checkout, theme, SEO, extensions, or everyday management.

A rebuild makes more sense when the current base is unmaintainable, full of old edits, or unable to support the commercial workflows you need. Start with a technical audit before deciding.

In an old OpenCart store, first check the OpenCart and PHP versions, theme, installed extensions, OCMOD/VQMOD changes, error logs, database, checkout, payments, shipping, SEO URLs, and backup.

The goal is not to change everything at once. First identify what creates risk for sales, security, and maintenance, then prioritize the improvements.

A custom OpenCart extension brief should explain the problem it solves, who uses it, what data goes in and out, which systems connect, which OpenCart version you use, and what results are acceptable.

Screenshots, sample orders, existing exports, API docs, and edge cases are useful. This helps OpenCart extension development start with a clear scope.

A custom OpenCart extension is far more likely to keep working after an upgrade when it avoids core-file edits, follows a clean structure, has documentation, and is tested on staging before the live store changes.

No upgrade should be treated as automatically safe. Compatibility checks are needed for the theme, events, OCMOD/VQMOD, payments, courier integrations, and custom code.

Adapt an existing OpenCart extension when its license, code quality, and architecture allow clean changes without hurting maintenance. Build a new one when the existing module is restrictive, unmaintained, or does not match the business workflow.

The decision should come from a technical review, not only from initial cost. Sometimes a cheap adaptation becomes more expensive than a clean implementation.

To improve OpenCart checkout, remove unnecessary fields, show shipping and payment options clearly, avoid slow scripts, review the mobile experience, and make sure payment callbacks update orders correctly.

Checkout improvement should be measured with real data such as cart abandonment, payment errors, loading time, and customer questions before purchase.

Abandoned carts drop when OpenCart checkout is fast, shipping cost appears early, popular payment methods are available, unnecessary fields are removed, and reminder emails are sent correctly where allowed.

Before adding a new marketing tool, check for technical friction: slow checkout, hidden fees, payment failure, poor mobile experience, or email deliverability issues.

OpenCart connects with ERP and myDATA either directly or through middleware, depending on the ERP, document flow, VAT rules, order statuses, and when the invoice or receipt must be issued or updated.

A correct implementation needs mapping for products, customers, taxes, payment methods, and orders. For complex flows, review custom OpenCart integrations.

OpenCart needs invoicing automation when order volume makes manual issuing slow or error-prone, especially when VAT mistakes or mismatches appear between the store, ERP, and accounting process.

Before automating the flow, agree rules for receipts or invoices, cancellations, credit notes, cash on delivery, intra-EU sales, and order-status updates.

Payment gateway choice depends on the bank or provider, fees, installments, IRIS or wallet support, compatibility with your OpenCart version, and correct order status updates after callback.

For core criteria, see the OpenCart payment methods guide.

Common causes include a wrong callback URL, domain or SSL changes, firewall blocking, incorrect order statuses, payment extension incompatibility, or an error in checkout after the customer returns from the bank.

Check logs, payment settings, and a real payment flow before changing production order statuses.

Order emails may fail because of wrong SMTP credentials, DNS changes, SPF/DKIM/DMARC issues, blocked mail ports, old PHP mail settings, or an extension error after order creation.

Start diagnosis with OpenCart error logs, mail server logs, and an SMTP test. Also see why SMTP is usually better than PHP mail.

The license is the right to use the extension, updates are new versions or fixes, and technical support is help with installation, diagnosis, or configuration.

If you need renewal or license review, start from the OpenCart extension license renewal page.

Yes, but it needs planning for domains, languages, currencies, categories, product descriptions, SEO URLs, hreflang, payments, and shipping per store.

For a commercial store with multiple markets, design the architecture before importing many products or launching campaigns.

To add IRIS payments to OpenCart, you need a provider or bank gateway that supports IRIS, a compatible payment extension, and a correct callback flow so the order is updated after payment.

Check whether your Viva, EveryPay, or bank gateway contract includes IRIS and review the OpenCart payment methods guide before requesting a custom connection.

There is no one-size-fits-all payment gateway for every OpenCart store. The right choice depends on fees, installments, IRIS, Viva or EveryPay support, your existing bank contract, OpenCart version, and callback reliability.

For a neutral evaluation, start with the OpenCart payment methods guide and request a compatibility check through contact if you already have a provider in mind.

Products are usually rejected by Skroutz when required fields are missing, price or availability is wrong, images are not publicly accessible, or the XML feed does not follow marketplace requirements.

For a more controlled export, see CSL Skroutz Feed Pro and test products with a real feed URL first.

Start from product data in OpenCart: correct model, manufacturer, GTIN or MPN where required, clear availability, tax-aware prices where needed, and images that open publicly without login.

When the feed needs marketplace-specific rules, CSL Skroutz Feed Pro or a custom feed integration can reduce manual cleanup.

Skroutz and Google Merchant feeds send products, prices, and availability for catalog visibility. Marketplace order sync is about orders coming back into OpenCart and needing acceptance, updates, and status handling.

For Skroutz products, see Skroutz Feed Pro. For Skroutz orders, see Skroutz Smart Cart.

To preserve SEO rankings during an OpenCart migration, map old URLs, create 301 redirects, review titles and metadata, set canonical URLs, regenerate the sitemap, check robots.txt, and monitor Search Console after launch.

For SEO URL and redirect management inside OpenCart, see CSL SEO Links.

Duplicate SEO URLs can appear when the same product belongs to multiple categories, paths change without redirects, filters are indexed, or multistore and language setups do not have clean canonical logic.

The fix is canonical review, clean URL structure, and 404/redirect monitoring with tools such as CSL SEO Links.

When a product or category URL changes, the old URL should return a 301 redirect to the closest relevant new URL. Avoid redirect chains and check 404s after deployment.

For everyday redirection and lost-path management in OpenCart, see CSL SEO Links.

Yes. Cloudflare can work with OpenCart for DNS, SSL, WAF, and static asset caching. It needs careful rules so cart, checkout, account, and payment callback URLs bypass full-page cache.

Review the OpenCart hosting requirements and request a check if you use aggressive cache or a custom checkout.

Cart, checkout, account, and payment callback pages contain dynamic customer and session data. If they are full-page cached, customers may see the wrong cart, the wrong login state, or failed order-status updates.

Optimization should target assets, database, and server cache with exclusions for critical flows. See the OpenCart performance optimization service.

If you suspect a hack, do not randomly delete files before taking a snapshot. Restrict admin access, change passwords, preserve logs, check recently changed files, and stop suspicious cron jobs or redirects.

For structured diagnosis, open a request through the support questionnaire or review the OpenCart security audit service.

Compare files against a clean OpenCart version and known extensions, check modification dates, unknown PHP files, suspicious redirects, and code that does not belong to your theme or plugins.

For general hardening, see the OpenCart security guide. If there are signs of compromise, prefer a technical audit.

If you have a clean backup from before the compromise, restoring can be the fastest path, but the original cause must still be fixed. If the backup is old or uncertain, clean the current store, audit files, and rotate passwords.

Before deciding, review the backup guide and consider a security audit so the issue does not return.

A proper OpenCart backup should include the database, all files, images, downloads, storage, config.php, admin/config.php, .htaccess, custom OCMOD/VQMOD changes, and any custom integrations.

The OpenCart backup guide helps confirm whether the backup can actually be restored.

For an active OpenCart e-shop, the database should usually be backed up daily or more often because orders and customers change. Files can follow a different schedule, but should be backed up after theme, extension, or image changes.

Before every upgrade, keep a separate full backup.

Staging shows whether the theme, extensions, payments, courier plugins, feeds, and custom code work before the live store changes. This reduces the risk of breaking checkout or losing orders.

For a structured process, see the OpenCart upgrade service.

OpenCart emails often go to spam when SPF, DKIM, or DMARC are missing, when PHP mail sends without a clear sender identity, when the domain has poor reputation, or when the message content looks like bulk mail.

For more reliable sending, use SMTP and correct DNS setup, or review email hosting.

For most professional stores, SMTP is better than PHP mail because it supports authentication, better logging, and a cleaner relationship with SPF, DKIM, and DMARC.

PHP mail can work in simple setups, but for e-shop order emails a reliable SMTP provider is the safer choice.

SPF, DKIM, and DMARC are DNS settings that help recipients confirm that e-shop emails are sent by authorized services and are not spoofed.

Without correct setup, order, invoice, and password reset emails may land in spam or be rejected.

For a Greek OpenCart store, start with correct tax classes, tax rates, and geo zones. Usually you create a Greek VAT rate, connect it to a tax class, and assign that tax class to taxable products.

Always confirm the accounting policy with your accountant, especially if you sell to other countries, B2B customers, or products with different VAT rates.

The right choice depends on your audience and accounting flow. Retail e-shops usually show prices including VAT, while B2B setups may need net prices and clear tax breakdown in checkout.

The important part is consistency across catalog, cart, order, invoice, and ERP so you avoid rounding differences or wrong totals.

Use geo zones and separate tax rates for countries or regions that need different tax treatment. Then connect those rules to the correct tax class.

For sales outside Greece, B2B transactions, or special exemptions, the technical setup should follow written guidance from your accountant or tax advisor.

Differences usually come from the wrong tax class, different rounding, discounts calculated before or after VAT, shipping tax, or incorrect mapping during ERP sync.

Check a real order line by line. If you use SoftOne, review the SoftOne Connector for OpenCart so tax fields are mapped correctly.

Take a database backup before an upgrade, extension installation, bulk product import, SEO URL changes, data cleanup, or any work that affects orders and customers.

The backup must be restorable, not just an SQL file that exists somewhere. Review the OpenCart backup guide for a practical checklist.

The table prefix is the prefix used for database tables, such as oc_ in many installations. It helps OpenCart identify its own tables and can allow multiple installs in one database only when they are carefully separated.

Do not change the prefix on a live store without a full backup and checks for config.php, admin/config.php, and custom SQL in extensions.

Start with server slow query logs, large product/category tables, heavy filters, custom reports, and extensions that query without proper indexes.

The fix may involve indexing, log cleanup, extension SQL changes, or better hosting. For a commercial store, review the OpenCart performance optimization service.

Old sessions, temporary carts, logs, old search terms, or unused extension records can often be cleaned, but orders, customers, and tax/order totals should not be removed without a clear reason.

Before any cleanup, take a database backup and test the query on staging or a copy of the database.

Use the HTTP Status & Headers Checker to see whether a URL returns 200, 301, 302, 404, or another status, and which headers the server sends.

It is useful for redirects, canonical issues, Cloudflare cache, blocked feeds, and callback URLs from payment or courier integrations.

A QR code can be used for product links, pickup instructions, printed documents, packaging, payment instructions, or offline campaigns that lead to a specific page.

For quick creation, use the free QR Code Generator and test the final QR before printing it.

If a log, webhook, or API response contains a Unix timestamp, use the Timestamp Converter to convert it into a readable date and time.

This helps debug payments, cron jobs, courier callbacks, and sync jobs that write times in UTC or ISO format.

Image to Base64 is useful when a small image is needed as a data URL in an email template, demo, technical example, or temporary integration where you do not want a separate public file.

For normal product images, use image files instead of Base64 because Base64 increases HTML size. See the Image to Base64 tool.

A postcode API can check whether the customer entered a valid Greek postcode, suggest the place, or support courier rules before checkout is completed.

For Greek postcodes, see the ELTA Postcode API, which includes a live test form and endpoints for postcode and place lookup.

The ELTA Postcode API provides two main GET endpoints: /api/postcode/{postcode} for lookup by 5-digit postcode and /api/place/{place} for lookup by Greek place prefix.

The response is JSON with ok, type, query, count, and results, so it can be used by browser tools, backend services, or integrations.

Yes. It can help validate postcode input, compare place names with shipping details, and support custom shipping rules before an order is sent to a courier web service.

Full automation usually needs a custom connection for each courier, checkout flow, and business rule. Review custom OpenCart integrations.

Every custom API connection should include input validation, secure credentials, rate limits where needed, clear logging, timeout handling, and correct order-status mapping.

Do not leave callbacks or admin endpoints open without access control. For secure planning, review custom OpenCart integrations.

We mainly support OpenCart 3.x and 4.x, with compatibility checks for the theme, extensions, and PHP version.

For older stores, we first assess whether maintenance, patching, or a structured OpenCart upgrade is the better path.

Yes, we can review OpenCart 2.x stores, but support is legacy and depends on PHP, hosting, extensions, and available source code.

When the risk is high, we recommend a staging migration to a newer version instead of short-lived fixes on the live store.

Yes. We start with an audit of the version, theme, extensions, custom code, logs, hosting, and core commercial workflows.

After the audit, we propose a clear plan for support, upgrade work, performance, or fixes without changing working features unnecessarily.

To get a live quote, start from the OpenCart quote page and then open a new protected quote. The request requires login so private details, attachments, and our response stay connected to your account.

1. Choose the work type, such as plugin, theme, integration, mobile app, or another custom scope.
2. Describe the outcome you want and what already exists in the store.
3. Send technical context, such as OpenCart version, theme, extensions, screenshots, logs, or API details.

Repeatable requests may receive immediate pricing. More uncertain or larger scope goes through structured review before a final quote is sent.

An accurate OpenCart quote needs clear technical and commercial context. The more specific the details are, the fewer clarifications are needed before pricing.

• Store details: OpenCart version, active theme, key extensions, and URL where available.
• Work scope: what should change, which problem it solves, and the expected outcome.
• Technical inputs: screenshots, logs, staging access, API documentation, or sample files where integrations are involved.
• Priority: deadline, live issue, budget range, or constraints we should know before reviewing.

If you only know the business goal, open a new quote request and explain what you want to achieve. For the general process, review the quote page first.

OpenCart can handle thousands or tens of thousands of products when hosting, indexes, images, filters, and extensions are designed correctly.

The real bottleneck is usually the database, slow queries, heavy images, or checkout load. Review the OpenCart performance optimization service.

Start with suitable hosting, caching, CDN, image compression, GZIP/Brotli, minification where it does not break the theme, log cleanup, and slow database query review.

For a live store, measure before and after so it is clear which change actually improved LCP, TTFB, and checkout response.

IRIS integration depends on the bank or payment provider offering the service, the available API credentials, and the right OpenCart payment module.

Before going live, test sandbox or test transactions, order statuses, redirects, callbacks, and failed-payment handling.

Yes, when the payment gateway or bank supports installments and there is a compatible OpenCart module for that workflow.

We check rules by card, amount, product, currency, and order status so installments appear correctly at checkout.