Silky Drum

a wholesale coffee shop connected to 1C

I built the WooCommerce wholesale flow from supplied designs and connected product imports, orders and invoice PDFs to the company’s 1C workflow.

Field
Coffee wholesale / Russia
Built with
WordPress / WooCommerce / JavaScript
Project year
2024–2025
Public wholesale account login. Current Silky Drum site, October 2026. Catalogue access requires an account.
Project detail

Public wholesale account login. Current Silky Drum site, October 2026. Catalogue access requires an account.

The challenge

The coffee roaster’s growing wholesale audience needed a separate ordering channel from its consumer shop. Supplied designs had to become a working WooCommerce storefront connected to the company’s 1C accounting workflow.

The approach

I implemented the supplied catalogue, product, basket and checkout designs in WooCommerce. I connected products and orders to 1C, then added PDF invoice generation and email delivery on the website side.

How orders and invoices move between systems

An explanatory diagram of the documented work, not a screenshot of the product or a complete system architecture.

Product catalogue

  1. 1C product records
  2. GUID matching
  3. WooCommerce products

Order and invoice

  1. WooCommerce order
  2. 1C invoice and fulfilment documents
  3. Website-generated PDF
  4. Email to the customer

The project, in detail

Public login and registration screens from October 2026 accompany images from the original store manual. The catalogue requires an account, so customer orders, invoices and private account pages are not shown. Original Russian text is retained.

A separate shop for wholesale buyers

I built custom WooCommerce templates for the wholesale purchase flow using designs supplied by another team. The public account screens shown here are from October 2026. They show the entry point; the catalogue and customer orders require login.

Public registration with email and delivery-region fields. October 2026. The original Russian interface is retained.
Project detail

Public registration with email and delivery-region fields. October 2026. The original Russian interface is retained.

The same product in WooCommerce and 1C

I matched imported products by their GUID identifiers. The store can refer to the same item as the accounting system even when the visible product name changes. The archive screens show product editing and variants from the original store manual.

Product administration documented in the original store manual.
Project detail

Product administration documented in the original store manual.

Configuring product variants in the store administration.
Project detail

Configuring product variants in the store administration.

1 of 2

Orders that lead to an invoice

I sent new orders to 1C, where the invoice and fulfilment document were prepared. On the website, I generated the invoice PDF and sent it to the customer by email. The diagram explains this exchange without exposing real customer documents.

Delivery-region message from the original store manual. Historical Russian interface, not a current delivery promise.
Project detail

Delivery-region message from the original store manual. Historical Russian interface, not a current delivery promise.

An espresso recipe panel from the historical Silky Drum storefront.
Project detail

An espresso recipe panel from the historical Silky Drum storefront.

1 of 2

On a smaller screen

Real phone-sized browser captures from October 2026. They show the current site; content and product details may have changed since delivery.

Mobile wholesale registration. Current public site, October 2026; no account was created.
Project detail

Mobile wholesale registration. Current public site, October 2026; no account was created.

The outcome

Delivered

A wholesale purchasing flow connected to product records, orders and invoice documents in 1C.

Details of Silky Drum

How did the wholesale shop stay aligned with 1C?

Products were matched by GUID identifiers. New orders went to 1C, and the resulting invoice documents returned to customers as PDFs by email.