Matjar provides an Arabic and English storefront, customer accounts, a variant-aware catalog, cart and checkout, inventory, orders, returns, and content and operational tools within one administration area.

Writable locations during installation

PHP must be able to create .env and write to public/uploads plus storage and its app, app/backups, app/private, cache, cache/sessions, cache/rate-limits, and logs branches. Ownership and permissions follow the hosting provider’s permission model; 777 permissions should not be granted to all files.

Preparation checklist

• Domain points to the host
• Valid SSL certificate
• Database and credentials
• Correct PHP and extensions
• Secure administrator email
• Original package retained safely

Choose the deployment layout

ACCOUNT is a placeholder for the actual cPanel account name, and example.com is replaced by the domain connected to the installation.

Detailed cPanel installation

Post-installation checks

• Open the homepage and /signin over HTTPS
• Sign in as the administrator and open /admin/license
• Upload a test image to verify public/uploads access
• Confirm that requests to /.env and /app/ return 403 or 404 without content
• Open System Health and review reported issues

Configure Cron in cPanel

Under Cron Jobs, add a task every 5–15 minutes. Use the PHP CLI path supplied by the hosting provider and the actual absolute installation path. Examples:

The task runs due automatic backups and cleans expired checkout sessions, manual orders, and stock reservations. Cron error email should remain enabled during the first test; web traffic is not a reliable scheduler.

Common cPanel issues

After installation, the public storefront remains available while administration pages stay locked until a valid license is activated. The complete process is managed at /admin/license.

Obtain the license code

Add the code and activate Matjar

1. Activate the license, then open /admin/system-health and resolve red requirements.
2. Complete the store name, logo, URL, email, address, currency, country, and tax.
3. Configure SMTP and send a test before enabling email verification, administrator OTP, or newsletter flows.
4. Configure Stripe Test or manual payments, then shipping and every method’s price.
5. Create categories and review all products, prices, stock, images, and usage rights.
6. Run a complete order: variant product, payment, invoice, fulfillment, label, tracking, and notification.
7. Create a backup, configure Cron, review privacy/shipping/return policies, and then launch.

General settings /settings

Operating settings /admin/store/settings

• Store email, phone, and address
• Currency and country
• Low-stock threshold
• Order-number prefix
• Store enabled/disabled
• Returns and return window
• Cart suggestions
• Contact-map address

Set manual unpaid-order expiry between 1 and 168 hours, guest-order limits by IP and email within a time window, and whether cash on delivery is exempt from expiry. The default expiry is 24 hours.

Available currencies

Arabic is the fixed source language. General Google Translate support defaults to en,sv,de,fr,es,tr,it,nl and accepts a comma-separated list. The catalog also supports pt, pl, da, no, fi, ru, uk, el, ro, cs, hu, he, fa, ur, hi, id, ms, th, ja, ko, zh-CN, and zh-TW. Direction switches automatically for Arabic, Hebrew, Persian, and Urdu.

Translating product fields from Arabic to English

In the product form, use “Translate empty EN fields” to preserve existing copy, or “Translate and replace EN” after confirmation. The limit is 40 requests per minute per session and 12,000 characters per request.

Storefront layout /admin/store/layout

• Catalog view: grid, rows, or large grid.
• Homepage: all products with infinite loading, one category, or blocks from several categories.
• Default category and product image frame width 320–1400, height 240–1200.
• Footer: show payment image, copyright, privacy/terms, and language switcher; place each at Left/Center/Right.

Theme Builder /admin/theme-builder

Start with Matjar Blue, Emerald, Indigo, Amber, or Slate, then customize the available brand, status, light, and dark colors. Adjust card/button/input radii, sidebar widths, content width, density, shadows, logo position, and up to 20,000 characters of custom CSS.

Create a category /admin/store/categories

Enter Arabic/English names, slug, parent, default product type, order, both descriptions, an uploaded image, and the Enabled/Homepage flags. Use a short, stable Latin slug because URLs and CSV import depend on it.

Built-in product types

A type selects relevant specification and option fields—for example storage/RAM for electronics, size/material for clothing, concentration/volume for fragrance, or ISBN/language for books. Built-in types and properties are available directly; custom type and property creation is not available in administration.

Open /admin/store/products and select “Add product.” Start with required fields, then complete content, pricing, stock, images, and options.

Writing product copy

• Short description: 1–3 sentences with the key benefit and differentiator.
• Full description: use, materials/ingredients, sizing, box contents, care, and truthful warnings.
• Specifications: exact, comparable values—not marketing phrases.
• Delivery note: confirmed preparation times or special conditions only.

Image upload

• Formats: JPG/JPEG/PNG/GIF/WebP, up to 10MB per image.
• Upload several images and drag to reorder; the first is primary.
• The detail view displays up to 12 images. The 250×250 recommendation is advisory; no automatic resize is performed.
• New images can be removed before saving. Existing images offer “make primary,” but the current form has no clear direct delete action.

Gemini image analysis

Enable analysis in store settings, enter a Gemini API key, and choose a model (default gemini-2.5-flash-lite). The first image can suggest names, descriptions, brand, and visible specifications in fill-empty or replace mode. It does not generate price, stock, or SKU; review every suggestion.

Import from a product URL

The tool fetches an HTTP/HTTPS page up to 2MB and four redirects, then extracts JSON-LD Product, Open Graph, Twitter data, title, description, brand, SKU/model, price/currency, and images. Select the desired fields and download up to six images.

CSV /admin/store/import

Product CSV export omits category_slug, so it is not a complete round trip. General JSON import/export is also not a substitute for a signed DB + files backup.

At /admin/store/inventory, monitor total, low/out-of-stock counts, reorder levels, inventory value at cost, and the latest 200 movements. CSV export is available.

Checkout verifies stock on the server, not only the browser. Successful payment commits the deduction; failure, cancellation, or expiry releases the reservation idempotently.

Methods are managed at /admin/store/payment-gateways. Enabling a row or uploading an icon does not create an API integration; checkout requires a real adapter and valid credentials.

Payment states

The transaction ledger is append-only and cannot be deleted from administration. It prevents duplicate provider references, more than one successful payment per order, and refunds beyond the total. A paid order cannot be moved back to Pending/Failed.

Available Stripe methods

Apple Pay and Google Pay are not independent gateways; they appear as eligible Stripe Payment Element wallet presentations based on account, buyer, device, and browser. Stripe.js collects card details; Matjar does not store them.

Bank transfer

Enable the method and put bank name, beneficiary, IBAN/account, BIC/SWIFT if needed, required customer reference, and deadline in the Arabic/English description. Sensitive information not intended for checkout should remain excluded.

USDT

State the network exactly (for example TRC20 or ERC20), wallet address, required asset, who pays network fees, and the required reconciliation reference. Blockchain connectivity and automatic wallet verification are not available.

Cash on delivery

State regions, conditions, and fees in the description and configure suitable shipping. COD can be exempted from manual-order expiry. Do not mark it paid before collection.

At /admin/store/shipping-methods, edit AR/EN name and description/instructions, flat cost, sort order, icon, and enabled state. Checkout displays enabled methods and their cost in the store currency.

These are initial rates in the current store currency, without conversion. Replace them with the actual rates agreed with the carrier. Pricing does not vary by address or weight; product weight is not used by this path.

Free shipping

Enable it, set the minimum, decide whether the threshold is before or after discounts, and write AR/EN messages using {amount} for the remaining amount.

/admin/store/orders provides search, filters, tabs, customer/address details, line items with options and SKU, totals, payment, shipping, event history, invoice, notes, and notifications.

Statuses

Daily actions

• Filter paid and unpaid
• Copy address, phone, and email
• Mark ready to ship
• Add tracking and notify
• Print single or bulk labels
• View/download HTML invoice
• Resend invoice link
• Review event history

Bulk actions include Mark as paid, Ready to ship, Mark sent without tracking, and label printing. Do not use deletion as a normal workflow; cancellation and refund preserve the record.

Invoice

The bilingual invoice includes customer, address, payment/reference, products, options, SKU, shipping, tax, and states. Download returns an HTML file for browser printing, not a generated PDF.

Tracking may be edited or Shipped undone before a final state; undoing temporarily hides the customer tracking link until it is added again.

Initial configuration

1. At /admin/store/settings, enable returns and set the day window; default is 14 days.
2. At /admin/store/return-instructions, enter AR/EN title, recipient, address, suggested carrier, email, phone, instructions, and packing note.
3. Review the published return policy so it matches implementation and local law.

Return flow

Customer reasons are damaged, wrong item, manufacturing defect, unsuitable, or other. Photos are private to the owner and order managers. The customer may cancel before store receipt and refund processing.

Open /admin/store/taxes and configure tax enablement, tax country, VAT rate, income-tax rate, tax label, whether catalog prices include tax, and whether shipping is taxable.

Country-specific rules

Enter one COUNTRY=RATE rule per line, up to 200 rules with a 0–100 rate. Codes and names are accepted, for example:

When the buyer’s country has no match, the default rate applies. The page previews the calculation, and the order/invoice records the rate and amount applied at purchase time.

At /admin/store/customers, view customer profile, orders, total spend, tickets, reviews, and loyalty points. Broader user management at /admin/users shows role, state, country, phone, IP, and dates, with permission-controlled editing, enabling, disabling, and deletion.

Use /admin/store/track-order for administrative lookup by order/customer. The public /track-order page requires order number plus matching email or phone and is rate-limited to prevent disclosure.

Newsletter

Subscription starts Pending and uses a confirmation link valid for 48 hours. Confirmed subscribers receive an unsubscribe link. Limits are 8 attempts/IP/hour, 2/email/hour, with a 15-second wait. Subscriber export is available in JSON for use with an external sending tool; built-in subscriber administration and campaign sending are not available. Sending requires tested SMTP, confirmed consent, and compliance with local requirements.

SMTP /settings/mail

On later edits, leaving the password blank preserves its previous encrypted value. The From address must be permitted by the SMTP provider.

Message templates /admin/message-templates

Edit AR/EN subject/body and variables, enable/disable, restore defaults, preview, and test. Events include verification, password reset, new member, contact, ticket creation/reply/close, order shipment, paid order alert to admin, and admin announcement.

Broadcast supports members, administrators, or everyone through internal/email delivery with delivery/error logs. Start with a small sample and do not send without recipient consent.

Pages /admin/pages

Enter AR/EN title, description, and fallback HTML, slug/path, icon, state, audience (guest/member/admin), parent, order, and menu categories. Drag/drop ordering, preview, and delete are available. Each page has independent SEO fields.

Visual builder /admin/visual-page-builder

Drag/drop, live Desktop/Mobile preview, saved element library, and safe image uploads up to 5MB. Containers include Structure, Hero, Rich content, Feature cards, Image+text, Stats, Testimonials, FAQ, Homepage blocks, Contact form, and CTA. Widgets include Heading/Text/Button/Image/Icon/List/Stat/Divider/Spacer/Nested structure/Safe HTML.

Project templates /admin/project-templates

System templates are Store landing, Support portal, and Service overview. Create custom AR/EN templates and apply them as Public or Members pages. System templates are read-only and cannot be deleted.

Blog

At /admin/blog, set title, slug, category, Draft/Published/Scheduled/Archived state, publication date, AR/EN excerpt, content, tags, cover image, and Featured. Comments start Pending and can be approved/rejected/deleted. Blog supervisors manage the blog without full administration.

Knowledge base & FAQ

/admin/knowledge-base manages AR/EN categories/articles with audience, tags, featured, order, search, views, and helpful rating. /admin/faq manages categories, AR/EN questions/answers, audience, state, and order.

Store customer support /support and /admin/store/support

A signed-in customer opens a ticket with or without a related order, selects Low/Normal/High/Urgent, and adds a message plus JPG/PNG/GIF/WebP/PDF attachment. The conversation remains in the account. Administration uses Open/Pending customer/Closed, staff assignment, SLA due dates, replies, and bilingual canned responses. Attachments are private to the ticket owner and customer managers.

General ticket center /admin/tickets

The administrative ticket center provides departments for sales, paid support, storefront, server requests, finance, and technical support, with priorities, states, closing reasons, and attachments. Customers access store support through /support; the general ticket center remains administration-only and has no separate public customer interface.

Contact /contact

Name, email, subject, and message are required; phone is optional, with Captcha/Honeypot/Rate limit and custom fields. Messages are stored and administrators are alerted. /admin/contact-messages is used to view/delete them; there is no built-in reply button, so reply through email or another channel.

Forms & fields

At /admin/forms, create guest/member/admin forms, success message, administrator notification and recipient email, then manage New/Reviewed/Archived. At /admin/custom-fields, add text, email, phone, number, date, url, textarea, select, radio, checkbox, or file and attach it to profile, ticket, contact, or form.

Global SEO /admin/seo

• SEO enabled
• Default AR/EN title and description
• Default keywords
• Open Graph image
• Default index/follow
• sitemap.xml
• Custom robots.txt
• Generate page metadata

Page fields include AR/EN meta title/description/keywords, Open Graph, canonical, robots, schema JSON, and share image. Output includes canonical, Open Graph/Twitter, and validated JSON-LD.

Quick writing rules

• Make each page title unique and direct; do not repeat the store name.
• Write an honest page summary rather than a keyword list.
• Use canonical for substantially similar paths.
• Do not treat account, checkout, or search-result pages as indexable landing pages.
• Test the final share image and URL after HTTPS is enabled.

Social sign-in /settings/social-login

Enter Client ID/Secret and Redirect URI for each provider shown on the page, and register that exact URI in the provider console. Keep secrets server-side, and test a new account, an existing-email account, and logout. Provider availability depends on this installation and the external app.

At /admin/store/reports, review sales, orders, customers, and products with available filters; use inventory, transaction, and return CSV exports for analysis and accounting.

Separate records

• /admin/store/payment-transactions: non-deletable payment/refund ledger.
• /admin/store/webhooks: provider events, state, duplicates, and errors.
• Message delivery log: channel, recipient, state, and error.
• /admin/error-logs: PHP errors, diagnostics, and resolution.

System roles

At /admin/roles, create a custom role with AR/EN name/description, slug, order, state, and exact permissions. Administrator has all permissions and cannot be deleted; a role assigned to users cannot be deleted until they are moved.

Store administrators /admin/store/admins

The primary administrator can turn a registered user into a limited Store manager and grant Products, Orders, Customers, Marketing, Settings, or Reports groups. Test the account after saving, and do not grant Settings to staff who should not manage payment keys or policies.

Practical model

Core security /settings/security

• Registration enabled/disabled
• Email verification
• Administrator email OTP
• Math Captcha
• Google reCAPTCHA site/secret
• Maximum login attempts
• Lockout duration
• Exact/Wildcard/CIDR IP blocks

Do not enable email verification or OTP before SMTP testing succeeds, or accounts may be locked out. Test in a private window while keeping the current administrator session open.

Advanced security /settings/advanced-security

Production essentials

• Correct HTTPS/APP URL, private .env, and debug=false.
• Unique passwords, separate primary admin, least privilege.
• Test backups/restore, Cron, and keep PHP/hosting patched.
• Do not share Stripe/SMTP/translation keys; rotate on suspicion.
• Review uploads, private attachments, and error logs regularly.

Create a backup /backup-wizard

.env is always excluded, as are private support/return evidence directories. Packages contain backup-info.json, version.json, and an installation-specific integrity signature. Without ZipArchive, DB-only .sql.txt can be created.

Automatic backups

Enable, choose every 1–8760 hours, retain 1–100 packages (default 7), and select SQL/JSON/uploads/files. “Save and run now” tests immediately. Reliable execution requires Cron.

Safe restore

1. Place the site in maintenance, create an external copy, and verify package version.
2. Web restore is disabled by default. Open it temporarily with MATJAR_BACKUP_RESTORE_ENABLED=true, then set it back to false.
3. The primary administrator reauthenticates and types RESTORE/استعادة. Matjar creates a safety backup and validates the signed package.
4. Web restore restores uploads only. DB/JSON, project files, and .env are never restored from the browser.
5. Restore SQL manually on the server in a controlled maintenance window, then run health checks, sign in, and test an order.

JSON Import/Export /admin/import-export

Supports settings/pages/templates, support/knowledge, forms/fields, store data, and newsletter subscribers. Import is up to 20MB for the reauthenticated primary administrator in Merge/Update or Replace selected tables mode. It excludes passwords and full user/role backup and does not include image files; use Backup Center for those.

Maintenance mode /admin/maintenance

Enable/disable, allow administrator bypass, write AR/EN title/message, and enter one Exact/Wildcard/CIDR allowed IP per line. Preview the visitor screen before saving. When enabled, the public site returns HTTP 503 and Retry-After: 900; sign-in/out, password reset, and webhooks remain available.

Site upgrade /upgrade-wizard

Modules /admin/modules

Core Content, Messaging, and System cannot be disabled. Optional Knowledge, Blog, Forms, Support, and Files can be toggled; disabling hides menus and blocks routes without deleting data.

Health check /admin/system-health

Use Recheck, Repair schema to create/repair tables/columns and remove duplicate page routes, and Create test log to verify error capture. Disk space is an error below 10% and a warning below 20%.

Error logs /admin/error-logs

View Total/Open/Critical/Resolved and filter by state/level. Records may include message, source, user/IP, date, file/line, request path, context, and stack trace. Actions include Mark resolved, Reopen, Delete selected, Delete resolved, and Create test log. Clearing all requires CLEAR or تفريغ.

Mandatory purchase test

1. Create a new customer on mobile.
2. Select a variant with limited stock and apply a coupon if available.
3. Choose shipping and complete Stripe Test or a manual method.
4. Verify order, transaction, stock, invoice, and email.
5. Fulfill, print label, enter tracking, and open it from the customer account.
6. Deliver, create a return, and test stock decision and refund.

Key routes

Scheduled command

Capability support summary