Knows Magento's tables
EAV, categories, order items and credit memos. Adea knows where things live and joins them without you having to explain the schema.
Stack · Magento
The Magento database is large and the names are hard to guess. Adea knows the tables and reads your own modules, so a webshop manager can ask "what sold best in shoes in September?" and get an answer that matches your rules for status and returns.
Which products sold best in the Shoes category in September?
Top 3 by units sold: Aero Runner (612), Pier Sneaker (448) and Nord Hiking Boot (301). Cancelled and returned orders are subtracted.
Sourcesapp/code/Shop/Reporting/etc/order_status.xml:12
The code Adea read · app/code/Shop/Reporting/etc/order_status.xml:12
<status code="complete" counts="true"/> <status code="closed" counts="false"/> <status code="canceled" counts="false"/>
The query Adea ran (read-only)
SELECT i.name, SUM(i.qty_ordered - i.qty_canceled - i.qty_refunded) AS qty
FROM sales_order_item i
JOIN sales_order o ON o.entity_id = i.order_id
WHERE o.state NOT IN ('canceled','closed')
GROUP BY i.name ORDER BY qty DESC LIMIT 3
EAV, categories, order items and credit memos. Adea knows where things live and joins them without you having to explain the schema.
Which statuses count as a sale? How are returns subtracted? Adea reads it in your modules and asks a developer if something is unclear.
Set up the questions you ask every week and get the answer on Monday morning. The agency can spend the time on something else.
Give read access to the repo and create a MySQL user that only has SELECT. Preferably point at a read replica.
CREATE USER 'adea_readonly'@'%' IDENTIFIED BY '…'; GRANT SELECT ON magento.* TO 'adea_readonly'@'%';
Yes. Adea reads the tables and the code in both.
Only if you open the tables. Close columns like email and phone per role.
The agency can approve the rules Adea has understood. Nothing has to change in the shop.