<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Justas Arbatauskis</title>
    <description>The latest articles on DEV Community by Justas Arbatauskis (@justas_arbatauskis_e220d6).</description>
    <link>https://dev.to/justas_arbatauskis_e220d6</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2445197%2F807bb635-245e-4864-b521-8e29dbad4f97.jpg</url>
      <title>DEV Community: Justas Arbatauskis</title>
      <link>https://dev.to/justas_arbatauskis_e220d6</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/justas_arbatauskis_e220d6"/>
    <language>en</language>
    <item>
      <title>Lithuanian name days as open data: JSON, CSV and a tiny Rust crate</title>
      <dc:creator>Justas Arbatauskis</dc:creator>
      <pubDate>Mon, 16 Nov 2026 09:39:39 +0000</pubDate>
      <link>https://dev.to/justas_arbatauskis_e220d6/lithuanian-name-days-as-open-data-json-csv-and-a-tiny-rust-crate-4dgg</link>
      <guid>https://dev.to/justas_arbatauskis_e220d6/lithuanian-name-days-as-open-data-json-csv-and-a-tiny-rust-crate-4dgg</guid>
      <description>&lt;p&gt;In Lithuania many people celebrate their &lt;em&gt;vardadienis&lt;/em&gt; (name day) almost as much as a birthday. Every day of the year has a few names attached to it, so offices, schools and families check the calendar to see who to congratulate today.&lt;/p&gt;

&lt;p&gt;I could not find a clean, machine-readable version of that calendar, so I put one together and published it under an open licence.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is in the repository
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;vardadieniai.json&lt;/code&gt; and &lt;code&gt;vardadieniai.csv&lt;/code&gt; – all 366 days with their names (data from Lithuanian Wikipedia, CC BY-SA 4.0);&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;vardai.json&lt;/code&gt; – a reverse index: name → days;&lt;/li&gt;
&lt;li&gt;a Rust crate, a Python package and a D package built on the same data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Repository: &lt;a href="https://github.com/ello-lithuania/lietuviski-vardadieniai" rel="noopener noreferrer"&gt;https://github.com/ello-lithuania/lietuviski-vardadieniai&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Rust
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight rust"&gt;&lt;code&gt;&lt;span class="k"&gt;use&lt;/span&gt; &lt;span class="n"&gt;vardadieniai&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;days_for&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;names_on&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;today&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;fn&lt;/span&gt; &lt;span class="nf"&gt;main&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// Names celebrated today (Europe/Vilnius time)&lt;/span&gt;
    &lt;span class="nf"&gt;println!&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Today: {}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;today&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;", "&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="c1"&gt;// Diacritics are optional: "azuolas" finds "Ąžuolas"&lt;/span&gt;
    &lt;span class="nf"&gt;println!&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Ąžuolas: {:?}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;days_for&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"azuolas"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nf"&gt;println!&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"9 November: {}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;names_on&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;11&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;9&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;", "&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is also a small CLI: &lt;code&gt;cargo install vardadieniai&lt;/code&gt;, then &lt;code&gt;vardadieniai&lt;/code&gt;, &lt;code&gt;vardadieniai 11-09&lt;/code&gt; or &lt;code&gt;vardadieniai --vardas azuolas&lt;/code&gt;. No network access, the whole calendar is compiled in.&lt;/p&gt;

&lt;h3&gt;
  
  
  Two details that took longer than expected
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Time zone.&lt;/strong&gt; "Today" has to mean today in Vilnius, not on the server. The crate carries a minimal EU daylight-saving rule instead of a time-zone database, so it stays dependency-free.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Folding diacritics.&lt;/strong&gt; People type &lt;code&gt;zivile&lt;/code&gt; for &lt;em&gt;Živilė&lt;/em&gt;. Searching compares folded strings (ą→a, č→c, ė→e …), but the output keeps the proper spelling.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  For people who are not programmers
&lt;/h3&gt;

&lt;p&gt;The same calendar with name search, today's and tomorrow's names and a printable PDF lives at &lt;a href="https://dovanasuvardu.lt/vardadieniai/" rel="noopener noreferrer"&gt;dovanasuvardu.lt/vardadieniai&lt;/a&gt;. Corrections to the data are welcome as GitHub issues.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>rust</category>
      <category>opendata</category>
      <category>showdev</category>
    </item>
    <item>
      <title>What breaks when you add Baltic parcel lockers to WooCommerce</title>
      <dc:creator>Justas Arbatauskis</dc:creator>
      <pubDate>Wed, 23 Sep 2026 14:10:56 +0000</pubDate>
      <link>https://dev.to/justas_arbatauskis_e220d6/what-breaks-when-you-add-baltic-parcel-lockers-to-woocommerce-2431</link>
      <guid>https://dev.to/justas_arbatauskis_e220d6/what-breaks-when-you-add-baltic-parcel-lockers-to-woocommerce-2431</guid>
      <description>&lt;p&gt;In Lithuania, Latvia and Estonia, "shipping" usually means a parcel locker. Omniva, DPD and LP Express (Unisend) terminals sit outside every supermarket, and most shoppers pick one by habit — courier delivery is the exception, not the default.&lt;/p&gt;

&lt;p&gt;So every WooCommerce store here needs a locker picker at checkout. It sounds like a solved problem: install the carrier plugin, tick a box, done. In practice the same handful of things break every time. This is the list I now check before I promise a client a date.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. A terminal list is not a shipping method
&lt;/h2&gt;

&lt;p&gt;The carrier gives you a list of terminals — in Lithuania alone that is well over a thousand entries, and across the three Baltic countries several thousand. Two mistakes follow from treating that list casually:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rendering it as a plain &lt;code&gt;&amp;lt;select&amp;gt;&lt;/code&gt;.&lt;/strong&gt; A few thousand &lt;code&gt;&amp;lt;option&amp;gt;&lt;/code&gt; elements land in the checkout HTML on every page load. Checkout gets heavier for every customer, including the ones paying by courier.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fetching it live from the carrier API on checkout render.&lt;/strong&gt; Now your checkout depends on someone else's uptime.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Cache the list and render a searchable field:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight php"&gt;&lt;code&gt;&lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="n"&gt;shop_terminals&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$country&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'LT'&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nv"&gt;$key&lt;/span&gt;  &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'shop_terminals_'&lt;/span&gt; &lt;span class="mf"&gt;.&lt;/span&gt; &lt;span class="nv"&gt;$country&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nv"&gt;$data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;get_transient&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$key&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nv"&gt;$res&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;wp_remote_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="no"&gt;TERMINALS_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;array&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="s1"&gt;'timeout'&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;15&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nf"&gt;is_wp_error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$res&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;// Stale data beats an empty checkout field.&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;get_option&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$key&lt;/span&gt; &lt;span class="mf"&gt;.&lt;/span&gt; &lt;span class="s1"&gt;'_fallback'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;array&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nv"&gt;$data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;json_decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nf"&gt;wp_remote_retrieve_body&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$res&lt;/span&gt; &lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nf"&gt;set_transient&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;DAY_IN_SECONDS&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nf"&gt;update_option&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$key&lt;/span&gt; &lt;span class="mf"&gt;.&lt;/span&gt; &lt;span class="s1"&gt;'_fallback'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;_fallback&lt;/code&gt; option is the part people skip. Transients expire; carrier APIs have bad mornings. Without a fallback the customer sees an empty dropdown and leaves.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Block checkout silently drops the field
&lt;/h2&gt;

&lt;p&gt;This is the one that costs the most time. Many carrier plugins were written for the classic shortcode checkout and hook into &lt;code&gt;woocommerce_review_order_after_shipping&lt;/code&gt; or similar. Switch the store to the block-based checkout and the terminal picker is simply not there — no error, no notice, just a missing field and orders arriving without a terminal ID.&lt;/p&gt;

&lt;p&gt;Check which checkout the store actually uses &lt;em&gt;before&lt;/em&gt; estimating the work. If it is the block checkout, you need a plugin that registers a proper block integration, or you write one. There is no CSS-level workaround.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The terminal ID has to survive to the label
&lt;/h2&gt;

&lt;p&gt;The picker sets a value. That value has to travel: session → order meta → admin screen → label API. It breaks at the last two steps most often.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight php"&gt;&lt;code&gt;&lt;span class="nf"&gt;add_action&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="s1"&gt;'woocommerce_checkout_create_order'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$order&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;$data&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nv"&gt;$terminal&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;isset&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$_POST&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'shop_terminal'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="nf"&gt;sanitize_text_field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nf"&gt;wp_unslash&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$_POST&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'shop_terminal'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="nv"&gt;$terminal&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nv"&gt;$order&lt;/span&gt;&lt;span class="o"&gt;-&amp;gt;&lt;/span&gt;&lt;span class="nf"&gt;update_meta_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="s1"&gt;'_shop_terminal'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nv"&gt;$terminal&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then put it somewhere a human can see it. The warehouse person packing the order works from the admin order list, not from the API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight php"&gt;&lt;code&gt;&lt;span class="nf"&gt;add_filter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="s1"&gt;'manage_edit-shop_order_columns'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="nv"&gt;$cols&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nv"&gt;$cols&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'shop_terminal'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'Terminal'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nv"&gt;$cols&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(On stores running HPOS the hook names differ — &lt;code&gt;manage_woocommerce_page_wc-orders_columns&lt;/code&gt;. Support both if you do not control when the client flips that switch.)&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Conditional required fields
&lt;/h2&gt;

&lt;p&gt;When a locker is selected, street and house number are meaningless — but WooCommerce still validates them as required for most countries. Customers type "-" into the street field, and that garbage ends up on the shipping label.&lt;/p&gt;

&lt;p&gt;Make the address fields conditional on the chosen method, and validate the opposite way: if the method is a locker, a terminal ID is required; if it is courier, the address is. Half-done validation here produces orders you cannot ship without phoning the customer.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Free shipping over X, but only for lockers
&lt;/h2&gt;

&lt;p&gt;The business rule is almost always "free to a locker over €50, courier always paid". That is two shipping rates with different free-shipping logic, not one. Also check the tax class on each rate — in the Baltics shipping is taxed, and a rate created by hand often ends up with "standard" when the shop uses a reduced class for some products.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Tracking links in the right email
&lt;/h2&gt;

&lt;p&gt;Each carrier has its own tracking URL pattern and its own idea of when a number becomes valid. Put the link into the &lt;em&gt;completed&lt;/em&gt; order email, not &lt;em&gt;processing&lt;/em&gt; — the number frequently does not resolve yet when the order is marked processing, and a dead tracking link generates support mail.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. What I test before handing over
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Order to a locker in each supported country&lt;/li&gt;
&lt;li&gt;Order by courier, address validated&lt;/li&gt;
&lt;li&gt;Terminal API unreachable (block it in hosts) — checkout must still work&lt;/li&gt;
&lt;li&gt;Free shipping threshold at €49.99 and €50.01&lt;/li&gt;
&lt;li&gt;Label generated from the admin order screen, terminal correct&lt;/li&gt;
&lt;li&gt;Tracking link opens the carrier page with the real parcel&lt;/li&gt;
&lt;li&gt;Checkout tested on the block checkout if the store uses it&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this is hard. It is just longer than the "install plugin, tick box" estimate everyone starts with, and every skipped item turns into a support ticket after launch.&lt;/p&gt;




&lt;p&gt;I build and maintain WooCommerce stores in Lithuania at &lt;a href="https://kokybiskasvetaine.lt/" rel="noopener noreferrer"&gt;kokybiskasvetaine.lt&lt;/a&gt;. There is a Lithuanian version of this topic with local carrier specifics &lt;a href="https://kokybiskasvetaine.lt/siuntu-pristatymas-el-parduotuveje-omniva-lp-express-dpd/" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
    </item>
    <item>
      <title>How to Create a Professional Website That Helps Your Business Grow</title>
      <dc:creator>Justas Arbatauskis</dc:creator>
      <pubDate>Sun, 06 Sep 2026 06:23:10 +0000</pubDate>
      <link>https://dev.to/justas_arbatauskis_e220d6/how-to-create-a-professional-website-that-helps-your-business-grow-158p</link>
      <guid>https://dev.to/justas_arbatauskis_e220d6/how-to-create-a-professional-website-that-helps-your-business-grow-158p</guid>
      <description>&lt;p&gt;How to Create a Professional Website That Helps Your Business Grow&lt;/p&gt;

&lt;p&gt;A professional website is no longer just an online business card. For many companies, it is one of the most important tools for attracting customers, building trust, and generating sales.&lt;/p&gt;

&lt;p&gt;Whether you run a small local business, an online store, or a growing company, your website should be fast, responsive, easy to use, and designed with both users and search engines in mind.&lt;/p&gt;

&lt;p&gt;What Makes a Good Business Website?&lt;/p&gt;

&lt;p&gt;A successful business website combines several important elements.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Clean and Professional Design&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;First impressions matter. Visitors should immediately understand what your business does and what action they can take.&lt;/p&gt;

&lt;p&gt;A clean layout, consistent typography, clear navigation, and high-quality images can significantly improve the user experience.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Mobile Responsiveness&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A large percentage of website visitors use smartphones. This means that a website needs to work properly on different screen sizes.&lt;/p&gt;

&lt;p&gt;Responsive design ensures that menus, buttons, images, forms, and content remain usable on mobile devices.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Fast Loading Speed&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Website performance affects both user experience and search engine visibility. Slow pages can cause visitors to leave before they even see your content.&lt;/p&gt;

&lt;p&gt;Optimizing images, reducing unnecessary scripts, using caching, and choosing appropriate hosting are some of the ways to improve performance.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Search Engine Optimization&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A website can look great but still receive very little traffic if search engines cannot understand its content.&lt;/p&gt;

&lt;p&gt;Basic SEO should include optimized page titles, meta descriptions, headings, internal links, descriptive URLs, useful content, and technically sound pages.&lt;/p&gt;

&lt;p&gt;Why Professional Website Development Matters&lt;/p&gt;

&lt;p&gt;Building a website is more than installing a theme and adding a few pages. A properly developed website should be structured around the business's goals and its target audience.&lt;/p&gt;

&lt;p&gt;For companies looking for professional website development, working with an experienced web development team can help create a solution that is easier to maintain, faster, and better optimized for long-term growth.&lt;/p&gt;

&lt;p&gt;A good website should also be scalable. As a business grows, you may need new functionality such as online payments, e-commerce features, customer accounts, integrations, booking systems, or custom applications.&lt;/p&gt;

&lt;p&gt;WordPress vs Custom Development&lt;/p&gt;

&lt;p&gt;For many small and medium-sized businesses, WordPress can be an excellent choice because it provides a flexible content management system and a large ecosystem of plugins and integrations.&lt;/p&gt;

&lt;p&gt;However, more complex projects may require custom development. The right solution depends on the project's requirements, budget, expected traffic, integrations, and future plans.&lt;/p&gt;

&lt;p&gt;The most important thing is not simply choosing the most technically advanced solution. It is choosing the technology that solves the actual business problem.&lt;/p&gt;

&lt;p&gt;A Website Should Be Built for People First&lt;/p&gt;

&lt;p&gt;SEO is important, but websites should ultimately be created for people.&lt;/p&gt;

&lt;p&gt;Clear information, intuitive navigation, readable content, fast loading times, accessible interfaces, and simple contact options all contribute to a better experience.&lt;/p&gt;

&lt;p&gt;When visitors can quickly find what they need, they are more likely to contact the business or make a purchase.&lt;/p&gt;

&lt;p&gt;Final Thoughts&lt;/p&gt;

&lt;p&gt;A professional website is an investment in your company's online presence. Good design, performance, SEO, mobile optimization, and reliable development all work together to create a website that can support business growth.&lt;/p&gt;

&lt;p&gt;If you are planning a new website or want to improve an existing one, professional website development services can help turn your ideas into a reliable and effective online platform.&lt;/p&gt;

&lt;p&gt;For businesses looking to create a modern website, you can learn more about professional website development at &lt;a href="https://kokybiskasvetaine.lt" rel="noopener noreferrer"&gt;Kokybiška Svetainė - svetainių kūrimas&lt;/a&gt;.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
